Skip to content

Conversation

@weswigham
Copy link
Member

Fixes #58909

I considered skipping the error at the callsite issuing the error if the node isn't from the context.enclosingFile, but remembering that at every callsite is much more cumbersome than just filtering the node's applicability for the output file under consideration within the error reporter itself.

@weswigham weswigham requested a review from jakebailey July 9, 2024 18:10
@typescript-bot typescript-bot added Author: Team For Milestone Bug PRs that fix a bug with a specific milestone labels Jul 9, 2024
@jakebailey
Copy link
Member

@typescript-bot cherry-pick this to release-5.5

@typescript-bot
Copy link
Collaborator

typescript-bot commented Jul 9, 2024

Starting jobs; this comment will be updated as builds start and complete.

Command Status Results
cherry-pick this to release-5.5 ✅ Started ✅ Results

@jakebailey
Copy link
Member

I think this is marked for 5.6, but this is such a simple change and we're already fixing a bunch of ID related stuff in the next patch.

@typescript-bot
Copy link
Collaborator

Hey, @jakebailey! I've created #59210 for you.

@weswigham weswigham merged commit de77dd4 into microsoft:main Jul 9, 2024
@weswigham weswigham deleted the isolated-declaration-quash-nested-errors branch July 9, 2024 23:03
DanielRosenwasser pushed a commit that referenced this pull request Jul 16, 2024
…e-5.5 (#59210)

Co-authored-by: Wesley Wigham <wwigham@gmail.com>
@sandersn sandersn removed this from PR Backlog Apr 22, 2025
@microsoft microsoft locked as resolved and limited conversation to collaborators Oct 16, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Author: Team For Milestone Bug PRs that fix a bug with a specific milestone

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Isolated declarations errors occur in third-party node_modules when they ship with original TypeScript source files

3 participants