Fix literal array key types false positive error #265
Conversation
This file contains hidden or 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
mspirkov
reviewed
Dec 7, 2025
Contributor
mspirkov
left a comment
mspirkov
left a comment
There was a problem hiding this comment.
Are you sure you don't want to wait for the second version, where this problem is solved?
Author
|
Given the current rate of updates/development with nobody having time anymore for tooling (myself included if you look at the progress or lack thereof in psalm), it's probably going to be 2028 by the time the tools I need this for is updated to v2 (which again is mostly due to me not having time :-( Btw is "non-falsy-string" fixed in v2 too? |
Contributor
|
I plan to add support for |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fix #264