fix: .length on chained method call results returns correct value#324
Merged
fix: .length on chained method call results returns correct value#324
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
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.
Summary
[1,2,3,4,5].filter(x => x > 3).lengthwas returning5(original array length) instead of2handleLengthPropertyhad no handler formethod_call/callexpression types — fell through togetStringLengthwhich treated the array pointer as a stringgetVariableTypeon the generated result and routes to the correct array/string length getterTest plan
arrays/filter-chain-length.ts— filter().length on both number[] and string[]🤖 Generated with Claude Code