mirror of
https://github.com/FriendsOfTYPO3/tea.git
synced 2024-11-10 00:36:13 +01:00
Mirror of TYPO3 Extension tea, managed by the Best Practice Team
https://typo3.org/community/teams/best-practices
eb909406fe
The following are changed: - web-dir: ".Build/public" => ".Build/Web" - bin-dir: not specified, defaulted to .Build/vendor/bin => ".Build/bin" The vendor-dir was alreaday ".Build/vendor" and is left unchanged. Since the above paths may be used in scripts, composer.json, build pipelines, configuration etc. it facilitates contribution across various extensions (and the core) if the same defaults are used. The goal of patches related to #802 is to unify the paths across TYPO3 extensions, specifically focusing on the "official" extensions (such as tea, Documentation examples extension etc.). - .Build has already been well established (and is used by "tea" as well. - web-dir (".Build/Web") is currently not used consistently (across official extensions). Either ".Build/public", ".Build/Web" or ".Build/web" or "public" is used. We use ".Build/Web" now as that is already well established in "styleguide" and other extensions. (This choice is not better than the other, but is more commonly used and has led to a consensus in preliminary decision making process.) - bin-dir: Here ".Build/bin" is mostly used (if defined at all) - vendor-dir: Here ".Build/vendor" is mostly used (if defined at all) Related: #802 |
||
---|---|---|
.ddev | ||
.github | ||
.gitlab | ||
Classes | ||
Configuration | ||
Documentation | ||
Resources | ||
Tests | ||
tools | ||
.editorconfig | ||
.eslintignore | ||
.eslintrc.json | ||
.gitattributes | ||
.gitignore | ||
.php-cs-fixer.php | ||
.phpstorm.meta.php | ||
.prettierrc.js | ||
CHANGELOG.md | ||
CODE_OF_CONDUCT.md | ||
composer.json | ||
ext_emconf.php | ||
ext_localconf.php | ||
ext_tables.sql | ||
LICENSE | ||
package.json | ||
phive.xml | ||
phpcs.xml | ||
phpstan-baseline.neon | ||
phpstan.neon | ||
README.md | ||
stylelint.config.js |
Example TYPO3 extension for code quality checks and automated tests
This TYPO3 extension, based on Extbase and Fluid, is an example of best practices in automated code checks, unit/functional/acceptance testing and continuous integration.
You can also use this extension to manage your collection of delicious teas.
Presentation at the TYPO3 Online Days 2021
At the TYPO3 Online Days 2021, Oliver Klee held a session where her presented our approach for automating the code quality of extensions.