Leverage conditional types #99
Merged
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
This should help downstream projects stop wondering if null checks are necessary.
greg0ire
commented
Dec 11, 2022
| * : mixed | ||
| * ) | ||
| * ) | ||
| * ) |
There was a problem hiding this comment.
Docs: https://psalm.dev/docs/annotating_code/type_syntax/conditional_types/
I checked that it works with @psalm-trace in a test
SenseException
approved these changes
Dec 11, 2022
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.
This should help downstream projects stop wondering if null checks are necessary.
For instance, when I try running Psalm on
doctrine/ormwith2.1.x@dev, at the moment I still get 100 errors despite #95 . A lot of them are about possibly null arguments, when the argument is$someToken['value'].