-
-
Notifications
You must be signed in to change notification settings - Fork 67
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
Undefined property: PhpParser\Node\Stmt\Property::$type #14
Comments
So, with #9 we discovered there can be problems on custom projects. This might be due to PHP Mess Detector, Phan, Psalm, etc. Can you:
Drush requires If not... I am not sure. We'd need to dig into your project's dependencies more. |
I can reproduce this. Here is the information requested:
psy/psysh v0.9.9 requires nikic/php-parser (~1.3|~2.0|~3.0|~4.0) Thanks for the super useful utility! |
Is the Phar in your Drupal project's root? Can you try moving it into another directory and running it? Drupal Check is expecting psy/psysh may support ~4.0. But maybe the project only has 4.1 from when Drush was last updated. Now Drupal Check comes in expecting 4.2.1. But it adds Drupal's autoloader and now it's working with 4.1.0 and not 4.2.1. |
What I don't understand here and the vendor issue both: this is a phar file, why woud compontents outside of it matter? (Same goes for drush as well. I never studied PHAR much, I guess.) |
So there problem is this: Phars are an archive, and the project's In order to do static analysis, it needs to include the Drupal project's As soon as it loads Drupal.. any libraries from Drupal overwrite known namespace paths for Drupal Check. |
Reload phar autoload after? |
Focusing on this in #37. tl;dr of problem:
|
I have been trying to set this up in my gitlab CI and also tried running this locally on my macbook, and in both circumstances I get a lot of notices thrown to the screen/console like this:
Macbook:
Gitlab:
Any ideas what I may be doing wrong? In both circumstances we are using PHP 7.2
The text was updated successfully, but these errors were encountered: