Reason: support for visual studio code please

Created on 18 May 2016 · 13Comments · Source: reasonml/reason

would be really great! :) thanks

Source

hdcos

Most helpful comment

No one on the team uses VSCode right now so there aren't any support. But I've personally heard really good stuff about it and its perf. Tagging this as community project unless one of us start using VSCode =]/

chenglou on 19 May 2016

👍3

All 13 comments

chenglou on 19 May 2016

👍3

Yeah, this sounds like a great community project.

jordwalke on 19 May 2016

If there are tools for Atom, they can be ported over with relatively less work.

nmn on 22 May 2016

This seems relevant: https://marketplace.visualstudio.com/items?itemName=hackwaly.ocaml

kayceesrk on 9 Jun 2016

cc @Schmavery

chenglou on 9 Jun 2016

Looks like the plugin linked by @kayceesrk is what I was making, but finished. Would probably be pretty easy to convert to reason.

Schmavery on 9 Jun 2016

I've started working on a Reason extension for VS Code at vscode-reasonml. It's very minimal at the moment and just does some highlighting but it should improve quickly.

ghost on 15 Sep 2016

👍1

Sick. If this becomes established we'll include this (or leave it separate. There's a reason why all the plugins are included in the reason project right now) officially!

chenglou on 15 Sep 2016

I think a lot of people will like this (especially if you can use the debugger/type interaction from this plugin).

jordwalke on 16 Sep 2016

Just to give a status update on this, the vscode extension now supports type-on-hover and completion. I plan to take a look at adding support for the debugger soon.

ghost on 21 Sep 2016

👍2

Very cool. were you able to reuse a lot from the other VSCode Merlin plugin?

jordwalke on 21 Sep 2016

@jordwalke well I ended up implementing things a little bit differently in a few places. For example, using merlin protocol v3 and implementing the merlin functionality as a language server. The reason extension also does incremental synchronization instead of full synchronization. So I didn't reuse much directly but the OCaml plugin did help me understand several things early on about how merlin works.

The merlin language server part could in fact be drawn out into a separate package now but it might be nicer to port it to OCaml or Reason. But in that case, I think it's the kind of thing that should be distributed with the other tools so the user doesn't have to compile it on their own.

ghost on 21 Sep 2016

I think this is good to close, vscode is one of the best supported editors.