Do not call TypeSpecifier::specifyTypesInCondition with a non-null context in case the original context is null #1275
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
|
weird, |
|
1.6.x please :) |
|
And no, you didn't break anything, the same failure is currently on 1.7.x. |
…ntext in case the original context is null
|
Did I break something now? xD I think I didn't, but who knows. the strict mode and nette extension seem to be not happy |
|
You didn't. It's challenging to keep all the CI checks in older 1.6.x branch happy because they already contain fixes for 1.7.x... |
|
Thank you! |
|
Thx <3 |
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.
Closes phpstan/phpstan#7166
The title is a bit cryptic, the problems are scope "negations" via
IdenticalandEqualexpression handling like e.g. https://github.com/phpstan/phpstan-src/blob/1.6.4/src/Analyser/TypeSpecifier.php#L183