Skip to content

Skip missing nodes in formatting #48953

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 4, 2022
Merged

Conversation

andrewbranch
Copy link
Member

Fixes #32862 (not the first and not the last time)

@typescript-bot typescript-bot added Author: Team For Milestone Bug PRs that fix a bug with a specific milestone labels May 4, 2022
@andrewbranch andrewbranch requested a review from jakebailey May 4, 2022 17:24
Copy link
Member

@jakebailey jakebailey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume formatting is called from code fixes, then, given the original traces are all rooted from getCodeFixes, or should the test call via code fixes?

@andrewbranch
Copy link
Member Author

In this case you can just take my word that selection-based formatting caused the same crash prior to my fix. Occasionally a formatter crash can only be reproduced with synthesized nodes, but that wasn’t the case here.

@andrewbranch andrewbranch merged commit e26bc8a into microsoft:main May 4, 2022
@andrewbranch andrewbranch deleted the bug/32862 branch May 4, 2022 22:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.

Error: Debug Failure. False expression: Token end is child end in 'processChildNode' during 'getCodeFixes'
3 participants