[Call for help] Editor tooling: explore reporting syntax errors as you type


We’re trying out a new thing on the forums where we’ll post about issues and features we’re interested in getting help with. This typically also means that the particular issue or feature is a good opportunity to onboard new contributors. Keep a look out for more of these posts in the future, if you’re interested in getting started contributing, but don’t 100% know how to.

So, about this particular feature - we’re interested in exploring reporting syntax errors as you type (rather than only on save) via the editor tooling. Me and @cristianoc think this would be a good opportunity to onboard a new contributor.

Here’s a GitHub issue detailing what we’re interested in a bit more: https://github.com/rescript-lang/rescript-vscode/issues/448. It’ll likely help if you’re already somewhat proficient in OCaml, or interested in learning it. Essentially, we have (most) of the moving parts, but we need to do a bit of exploration as well as tie it all together in a good, sensible way.

Please reach out in the GitHub issue if you’re interested in getting involved in this!


I loved to join the party haha. I wish I can help you out!

1 Like

:clap: Please feel free to join the GitHub issue and we can take it from there!

1 Like

A short follow-up. @aspeddro has been doing some great work on enabling this feature. You can follow along the progress here: https://github.com/rescript-lang/rescript-vscode/pull/457


And another follow up - this is now merged and will be in the next release of the editor extension (1.4.0) :tada: Thanks to @aspeddro !