No syntax highlighting until the first edit #254#271
Merged
L-TChen merged 1 commit intobanacorn:masterfrom Jan 31, 2026
Merged
Conversation
… generated - Added `onDidChangeSemanticTokens` support to VS Code bindings. - Created a global event emitter for semantic tokens in `Main`. - Added `onUpdate` channel to `Tokens` that fires on highlighting generation. - Subscribed to `onUpdate` in `Main` to trigger the VS Code event. - Added regression test for `onUpdate` event emission.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The root cause is that VSCode was not notified that semantic tokens had changed.
This PR implements the onDidChangeSemanticTokens event to push updates to VSCode, and wires the extension's internal highlighting generation to this emitter, ensuring immediate visual refreshes upon every load.