Skip to content

Skip missing nodes in formatting - #48953

Merged
Andrew Branch (andrewbranch) merged 1 commit into
microsoft:mainfrom
andrewbranch:bug/32862
May 4, 2022
Merged

Andrew Branch (andrewbranch) merged 1 commit into
microsoft:mainfrom
andrewbranch:bug/32862

Conversation

@andrewbranch

Copy link
Copy Markdown
Member

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

@jakebailey Jake Bailey (jakebailey) left a comment

Copy link
Copy Markdown
Member

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
Copy Markdown
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
Andrew Branch (andrewbranch) merged commit e26bc8a into microsoft:main May 4, 2022
@andrewbranch
Andrew Branch (andrewbranch) deleted the bug/32862 branch May 4, 2022 22:07
@microsoft Microsoft (microsoft) locked as resolved and limited conversation to collaborators Oct 22, 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.

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

3 participants