Psalm 5.22.2 #11326
Merged
Psalm 5.22.2 #11326
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
greg0ire
approved these changes
Mar 1, 2024
derrabus
added a commit
that referenced
this pull request
Mar 1, 2024
* 2.18.x: Psalm 5.22.2 (#11326)
derrabus
added a commit
to derrabus/orm
that referenced
this pull request
Mar 1, 2024
* 2.18.x: Psalm 5.22.2 (doctrine#11326)
derrabus
added a commit
to derrabus/orm
that referenced
this pull request
Mar 1, 2024
* 3.0.x: Psalm 5.22.2 (doctrine#11326)
derrabus
added a commit
to derrabus/orm
that referenced
this pull request
Mar 1, 2024
* 3.1.x: Psalm 5.22.2 (doctrine#11326)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've bumped Psalm and regenerated the baseline.
Apparently, the baseline format has changed again (
<![CDATA[]]>all the things now, apparently) which is why the diff is pretty huge. Also, some errors regarding nullability have been reclassified.Then there's a new rule called
RiskyTruthyFalsyComparisonwhich bombs in our codebase. I've disabled it because I don't believe these errors are worth fixing on 2.x. We can think about enabling it in 3.x though.