Fix completions crash when IndexOfNode returns -1 #2258
+50
−1
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.
Completions panic with "index out of range [-1]" when requested inside
new Map([...])constructor at certain positions:Changes
checker.go:28914: Add
index >= 0bounds check before accessing type arguments array ingetContextualTypeForElementExpressionast.IndexOfNode()returns -1 when node not found in parent's element listNew test:
TestCompletionsInMapConstructorNoCrashverifies no crash at reported positionsOriginal prompt
new Map(...). #2254✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.