feat(semantic_tokens): add some lsp semantic tokens #512
Conversation
This file contains 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
mrtnvgr
approved these changes
Jun 20, 2023
|
I just hope that there's saner upstream default for semantic tokens, i.e. neovim/neovim#22981 so we don't need to play the catching game like this. @mrtnvgr FWIW you can usually double check these type of PR with tokyonight's semantic tokens One of the charm of catppuccin is we won't leave anyone behind (issues or pull requests) so don't feel the need to wait for another approval as long as you tested the PR before merging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add few/missing LSP Semantic Tokens:
@lsp.type.boolean@lsp.type.builtinType@lsp.type.number@lsp.type.typeAlias@lsp.type.unresolvedReference@lsp.typemod.class.defaultLibrary