Closed justclint closed 4 years ago
Upstream request https://github.com/mglaman/drupal-check/issues/156
Makes sense, however as you observed there's not much we can do unless the upstream library supports it first. In the meantime you could copy/override the BLT drupal-check command to use any arbitrary sets of directories (although you still won't be able to exclude directories).
we could potentially support an array of "to check" directories and then iterate through those. by default, we do modules/custom but we could do modules/custom/1 and modules/custom/3 but skip #2... would definitely tank performance but maybe that's ok? only those that need it would get it.
(so more explicit inclusion if using that feature by directory instead of supporting exclusion)
+1 to the above because we have several custom profiles in our project 🙏Easy enough workaround, we just run the command on our own in CI, but it would be nice not to have to run anything in addition to the BLT check command.
Actually, we're going to move Drupal Check integration to a community-supported plugin.
Drupal Check integration has been extremely resource-intensive to maintain, and many folks seem to prefer alternative solutions, plus it's less valuable in BLT 12 (for Drupal 9) than it was in BLT 11 (preparing for the D9 migration). Thus, it's better suited for a plugin.
We'll post more notes closer to the BLT 12 release date, but any additional features would need to be submitted as a PR on the plugin.
I want to... Exclude some directories from PHPStan / D9 validation check. Similar to how we can exclude file/directories in phpcs.xml.
I have 2 scenarios Im trying to solve for.
In our modules directory we have a custom module provided by a 3rd party service provider (not composer installed) that we need to remove from the check.
In our themes directory we are using pattern-lab which has its own composer vendor folder as well as some other stuff we don't want checked.
BLT Doctor output
System information
Thanks!