Replies: 2 comments 2 replies
-
I am with the same request - usage of phpcs, php-cs-fixer, etc. is something that miss a lot. Any ideas how to make them available based on currently documented setup? |
Beta Was this translation helpful? Give feedback.
0 replies
-
I deleted my previous posts so that all the info can live in one spot (where it will continue to be updated & maintained). I published a new lesson on how to set up Code Quality Tools in PhpStorm at https://courses.m.academy/courses/set-up-magento-2-development-environment-docker/lectures/36974633 |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I think it is necessary to test the code quality for all types of files:
All such tools that can analyze the quality of the code (phpcs, phpmd, ...).
You can make a CLI Command and a Watch Command.
I mean to be tested on everything that is custom created, possibly to be a configuration in which to mention the routes from
vendor/package
andapp/code/Package
.Beta Was this translation helpful? Give feedback.
All reactions