Using --analysis with Drupal gives a lot of issues due to loose array types about drupal-check HOT 4 CLOSED

Hey @mglaman, please let me know what you think about this, the code is pretty simple for this so made a PR in the hopes that you agree with me.
Thanks for all the work maintaining this.

from drupal-check.

Thanks for #278, @googletorp.

However, it may be a better solution to make it possible include some configuration file, e.g. phpstan.neon (in the project root), when running drupal-check (cf. https://github.com/mglaman/drupal-check#rollback-update-to-phpstan-level-2-for-deprecation-analysis). Any thoughts on this, @mglaman?

from drupal-check.

However, it may be a better solution to make it possible include some configuration

Please, just use PHPStan directly then. This package is meant to be an opinionated quick scan. Annotating array types can be annoying, but it helps fix buggy code.

from drupal-check.

@mglaman I agree in general that annotating array types is a great thing, but with Drupal use of render and form arrays, you get a bunch or warnings every time you extend core, which seems to defeat the purpose of writing clean code, if the framework you are building upon doesn't follow the same standards.

Can you offer some guidance on how to use this feature without getting overwhelmed by errors coming from Drupal Core?

from drupal-check.