[WIP] Port TypeScript PR #60195: Assume that type node annotations resolving to error types can be reused #1137
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.
Port TypeScript PR #60195: Assume that type node annotations resolving to error types can be reused
Plan:
Change Details:
The original TypeScript PR adds a check in the type node reuse logic to allow reusing type nodes that resolve to error types. This prevents cascading errors in isolatedDeclarations when there are already type errors in the source.
In the Go port, this needs to be added in
internal/checker/nodebuilderimpl.go
in thetryReuseExistingNonParameterTypeNode
function, right after theannotationType = b.getTypeFromTypeNode(existing, true)
call.Fixes #1118.
💡 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.