[WIP] Port TypeScript PR #60083: Don't issue implicit any when obtaining the implied type for a binding pattern #1136
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.
getTypeFromBindingElement
(line 17092) needs to callgetWidenedLiteralTypeForInitializer
instead ofwidenTypeInferredFromInitializer
widenTypeInferredFromInitializer
function needs to be updated to call the new functiongetWidenedLiteralTypeForInitializer
function needs to be addedThe TypeScript PR fixes an issue where implicit any errors were incorrectly reported when obtaining the implied type for a binding pattern. The key change is to use
getWidenedLiteralTypeForInitializer
instead ofwidenTypeInferredFromInitializer
in specific binding pattern contexts.Fixes #1116.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.