Add inlay hint support per LSP specification. #106
Merged
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.
Closes #103.
I'm retaining the support for the old-style RPC for now to avoid breaking the VS Code extension. I guess we'd technically increment the minor version of
syntax_tree
, release a new cut of the extension, and then increment themajor
version ofsyntax_tree
when removing support for the proprietary stuff! What a pain.It begs the question: should the LSP server be built into the
syntax_tree
gem, if it's likely to change frequently? I suppose that depends on the future of the parsing and formatting functions -- if some or all of the gem will be accepted as a built-in gem, then perhaps that would be a good time to split it up.