Conversation
anthony-malkoun
left a comment
There was a problem hiding this comment.
Does this then also lint a bunch of other directories besides the docroot/modules/custom directory?
| key "config.platform.php".--> | ||
| <config name="testVersion" value="7.1"/> | ||
|
|
||
| <exclude-pattern>*/docroot/*</exclude-pattern> |
There was a problem hiding this comment.
Won't this also then do everything in contrib as part of the lint?
There was a problem hiding this comment.
we have PHPCS_TARGETS in .env
|
Also, does |
a68eb67 to
4105d04
Compare
On-behalf-of: @salsadigitalauorg <sonny@salsadigital.com.au>
4105d04 to
eb7179a
Compare
|
I'm also encountering this problem. I noticed custom code I am reviewing is passing tests, even though it violates Drupal coding standards. Digging into why, I found this Could this <!-- Include these files -->
<file>docroot/sites/default</file>
<file>docroot/modules/custom</file>
<file>docroot/themes/custom</file>
<file>tests</file>Rather than excluding lots and lots of things, a smaller inclusions list could help project teams who use SDP. It would work better with IDEs, and either compliment, or negate the need for, a Also, if we renamed it to |
Currently
ahoy lintand PHPCS do not check any code indocroot/modules/customdue to the exclusion in phpcs.xml. We need to remove this exclusion so that CI can check for coding standard in custom modules.On-behalf-of: @salsadigitalauorg sonny@salsadigital.com.au