-
-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistency in drupal-check #269
Comments
@mglaman any suggestions to the above? 🤞🏼 |
This isn't inconsistent. Does that method exist in that interface or a different one? You're running with analysis and deprecations
See https://www.drupal.org/docs/develop/development-tools/phpstan/fixing-reports-of-undefined-methods |
Thanks for your reply! Yes, I know and also get how to fix this. My actual question is, why it only gives me this error when running The error is about a Core thing, so I should give the same error when following the guide from the wiki, which states to get a clean Drupal Core, require the custom module and running |
So when running the custom module outside of your normal project it doesn't error? The file being See the one without error:
And with:
The one with an error has your code properly placed in Drupal for analysis. Right now it's not possible to analyze a module outside of where Drupal would expect to find extensions |
How is drupal-check installed?
drupal-check is installed as a dependency to my project
Environment:
Describe the bug
Working on a private custom module and implementing drupal-check on every PR for that module.
When testing locally and in github workflows, it gives me no errors and everything seems to be fine.
Besides drupal-check, the module has dev requirements to Drupal core and requirements to contrib modules, which functionality is used/extended within this private custom module.
BUT, when including this module in an actual Drupal project and within this running drupal-check against the module, I'm getting an error,
I have also tried to follow the guide Drupal 9 Readiness, which gives the same non-error, as when running in the module directly.
Console output ran within module
Console output ran within a Drupal project
The text was updated successfully, but these errors were encountered: