fix(lsp): semantic token functions allow "0" bufnr #28849
Merged
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
justinmk
approved these changes
May 21, 2024
yes, documented at |
mfussenegger
approved these changes
May 21, 2024
huangyingw
pushed a commit
to huangyingw/neovim
that referenced
this pull request
May 31, 2024
aligns with ":help dev-patterns"
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.
Allows the following functions to adhere to the "0 for current buffer" rule (guideline?):
vim.lsp.semantic_tokens.highlight_token()vim.lsp.semantic_tokens.start()vim.lsp.semantic_tokens.stop()