-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Code folding incorrectly matches to an inactive } #5429
Comments
Code folding is lexer based. It doesn't know the values of preprocessor conditions. It looks like VS is initially folding this incorrectly as well, but doing another folding pass after inactive regions are available. We might be able to do something similar, but need a way to trigger VS Code to request ranges from us again (without having to edit the document). I've sent them a question on this, and am waiting for a reply. |
This is blocked on: microsoft/vscode#99914 |
Taking this out of tracking, as the blocking VS Code issue has been fixed. |
Although the blocking issue has been addressed by VS Code, it's still in insiders and not yet available in a general release. This will need to be delayed until the next VS Code release. This will also involve a dependency on that new VS Code version. |
The type we need is not yet present in @types/vscode 1.51.0. It's expected to be in 1.52.0. |
Originally reported at #407.
Use code
Bug: Code folding incorrectly matches to the inactive } instead of the active one that comes afterwards. The bug doesn't repro with VS.
The text was updated successfully, but these errors were encountered: