Javier Chávarri

Some more notes after discussing with @feihong, some things besides Antonio's gist: - Guide should explain how to work around issues with tests and docs when releasing in opam repository...

ftr https://github.com/melange-re/melange-examples/tree/9024b59cf1788fe1aa81f153423bec5d39a87123/examples/3-vite

cc @dmmulroy if you have ideas on the best ways to write this guide.

@andreypopp Thanks for the suggestion, I didn't consider that. Yes, I think that would avoid touching merlin because essentially we would be sidestepping the additions to the protocol by moving...

> e.g. on start we start ocamllsp for the default context, once `set-context` is used, we start another instance. I understand `ocaml-lsp` is quite heavy on memory, not sure how...

After some discussions with @andreypopp, and with vscode-ocaml users at Ahrefs (@davesnx), we are evaluating alternative implementations to the solution proposed in #1449. The main limitation of the context selection...

Thanks for the input @mnxn. After evaluating more carefully the folder layouts we have internally, I am thinking the solution I was suggesting (either with `ocaml.server.args` or `ocaml.server.contexts`) will be...

Update (just in case it helps): If I wrap the function body like ``` let foo = (arg: list(int)) => {arg;}; ``` or ``` let foo = (arg: someVariant) =>...

Another question: what's the best way to keep compatibility with `ocamlmerlin` and BuckleScript projects? `ocamlmerlin` is a crucial part of this extension to jump to definition etc, but the historical...

One thing I'm noticing when testing this branch is that when opening `.re` files with comments like `/* */`, merlin seems to choke: ``` # 0.02 lsp - debug send:...