-
-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tooling support #41
Comments
Besides the fork of Merlin, we'll also need our custom language server supporting the standard MS protocol (and running Merlin behind be scene to do the hard work, as you suggested!) I guess the biggest challenges will be:
|
I've been looking more into the On top of this, we may get away by submitting a patch to the |
Yes! |
I'd love to collaborate on LSP Proxy! It's a bit rough around some of the edges but it can be very helpful in understanding all of the messages that are going back and forth between the server and client. |
We'll need things like:
Formatting
Calling
caramel fmt
should reformat all inputs.Doc Generation
Calling
caramel docs *.mli *.rei --output ./docs
should create docs from those interface files.Language Server
What I'm considering atm is bundling Merlin within Caramel, so we have control over the subset of the language being accepted.
Calling
caramel language-server
should be the equivalent to booting a Merlin daemon, and we'll need a way to create the right .merlin files as well, possibly through a separate command that can be properly guided by a build system (e.g.caramel language-server setup ./path/to/lib/a ./path/to/lib/b ...
)REPL
TBD
The text was updated successfully, but these errors were encountered: