Give your feedback about rescript-webapi!

At my work, we were initially based on GitHub - TheSpyder/rescript-webapi: ReScript bindings to the DOM and other Web APIs and then decided to recreate our own bindings with only the basics. The rescript-webapi bindings were incomplete, vscode integration was poor and difficult to use for beginners.

I have 3 feedbacks to give:

We’re having trouble with vscode on autocompletion with our custom WebAPI bindings. I had mentioned this to zth here rescript-major-pains-with-editor-tooling/src/004.res at main · LeoLeBras/rescript-major-pains-with-editor-tooling · GitHub. Having Dom.* types and recreating bindings on top of them doesn’t allow rescript-vscode to provide suggestions.
What’s going to happen to Dom.* types?
Another issue: Rescript currently lacks official modules for using Fetch, for example. When I have a beginner developer coming into Rescript, he can’t write code to do simple things like an API call. He has to do some research to find out about rescript-fetch, but that’s not easy for a beginner. If your project GitHub - rescript-lang/experimental-rescript-webapi: Experimental successor to rescript-webapi becomes an official Rescript project (like rescript-core) with official documentation, this will change the game (in addition to the great improvements in json decoding + pattern matching for dicts).

ReScript is going in a great direction!