-
-
Notifications
You must be signed in to change notification settings - Fork 79
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
Many syntax errors with v4.0.0 after using vimeo/psalm
on php7.4
#67
Comments
Can you link a build? We test this component against 7.4 and 8.0, and besides some test fixtures, no PHP 8 syntax should be involved |
I think this one: https://github.com/Sylius/Sylius/runs/1629735084?check_suite_focus=true |
Return to |
If it helps, here another one: https://github.com/sonata-project/sonata-doctrine-extensions/pull/281/checks?check_run_id=1638983910 I have no idea, but looks like
|
Right, so What I was thinking is that your environment has a very old version of I wonder why it is the case for your CI though: it almost looks like the parser is running with old PHP version compat. I run pretty much the same stuff here: https://github.com/Ocramius/ProxyManager/runs/1626964286 Perhaps this is related to nikic/PHP-Parser#690 (comment) deep.in As you can see, the same tooling and runtime tests verify that there is no syntax issue on PHP 7.4, so I suggest reporting an issue in |
It was easier than it looked like, so if the PHP version is not provided, Psalm infers the PHP version from Configuring PHP version in psalm to 7.4 fixes the issue, e.g. executing:
|
Makes sense 👍 |
Description ----------- This should restore compatibility with laminas/laminas-code (see laminas/laminas-code#67). Commits ------- 245b5da Fix the Psalm configuration
Description ----------- This should restore compatibility with laminas/laminas-code (see laminas/laminas-code#67). Commits ------- 245b5da Fix the Psalm configuration
This PR was merged into the 1.9 branch. Discussion ---------- | Q | A | --------------- | ----- | Branch? | 1.9 1.10 master | Bug fix? | no | New feature? | no | BC breaks? | no | Deprecations? | no | License | MIT https://sylius-devs.slack.com/archives/C3EGDG9LY/p1634735181098300 This conflict is not documented in `CONFLICTS.md` anymore, was brought back in this commit: f80f42d However according laminas/laminas-code#67 and considering: https://github.com/Sylius/Sylius/blob/49b070933b32761de08475fafd6d86dca10d40ff/.github/workflows/application.yml#L104 should no longer be an issue. If it still is, then I guess the build will show it and there should be a new issue opened somewhere. Commits ------- 0ec9161 Remove undocumented conflict on laminas-code ^4.0
This renders the current Psalm baseline useless, see laminas/laminas-code#67 for further information. Hence, the baseline is removed.
v4.0.0 creates those enigmatic bugs on php7.4 after run vendor/bin/psalm --show-info=false:
I tested it on psalm 4.1, 4.2 and 4.3. Every cases are the same:
It occured in Sylius:
![Screenshot 2020-12-30 at 20 27 52](https://user-images.githubusercontent.com/39232096/103404900-9213b300-4b55-11eb-9d10-95b3650267d6.png)
The text was updated successfully, but these errors were encountered: