Add ron-lsp to README#589
Merged
Merged
Conversation
juntyr
approved these changes
Nov 4, 2025
juntyr
left a comment
Member
There was a problem hiding this comment.
Thanks for your work, this looks good to me!
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.
I built an LSP (and CLI) that, when coupled with a Rust project, allows diagnostics, auto complete, hover, go-to definition, auto-fix, etc by associating the RON object with a Rust type.
I implemented a separate tree-sitter for RON in this repo as the only one I could find was missing a fair amount of functionality. This is what is used for parsing / AST.
I implemented support for it in IntelliJ, VS Code, and Neovim as well, but any modern / LSP supporting editor should be able to integrate it easily.
I'm sure there are improvements that could be made and I absolutely welcome them!
CHANGELOG.md