https://caml.inria.fr/pub/docs/manual-ocaml/manual042.html

We can do this for Belt.Map as well

A lot of folks have been asking about a documented ReasonReact API

• mentioning stuff that's going away / deprecated
• going through the API and at a high level, talking about each function.

There are curried versions of that function, but we should talk about them under each top level, for example:

• useEffect
  talk about useEffect0, useEffect1, etc, here
• useState

Lot of packages depend on bs-react-native, such as this. We'll need to work with these package owners to migrate to the next release of reason-react-native.

Preliminary list from npm search:

• [x]

The thing is that when the codebase becomes large, it is really difficult to find what code has this problem. Same to to a vdom list change.

So Docusaurus is amazing for building sites and documentation and I really want to use it. It would be awesome to also port over the current homepage to a custom React component that can be used on the homepage too.

Relevant issue: jsdelivr/jsdelivr#18166

Update

So apparently jsdelivr will minify the main entry file and add .min. in its name. Since we check for the name. And the minified file could saves a lot of bytes and improve parsing speed for the bundler.

So we would save this default file provided by jsdelivr, check with what's provided in main field

Right now those gifs are using old Reason syntax. It would be great to update them to the latest syntax 🙂

I've noticed that there is an interface file for the bindings which is not very common. I just briefly looked at the implementation and interface files and I couldn't see any functions or modules hidden by the interface files, maybe it could be removed altogether and the documentation transferred to the implementation file?

If you prefer to keep the interface file, then it'd be nice to copy th

Just some ideas to reorganize the README in the docs.

• Put more useful info front & center - like what core modules we provide, and a brief explanation of what each module does
• move questions to a FAQ section (even though nobody is actually asking these questions)
• move other fluff content to an appropriate place (or delete)
• organize developer & contributor info in its own section

T

Hello, everyone!
There's this great tool called redoc that could benefit the project.
It generates a good looking documentation website using implementation files and docblocks.

I see two main benefits in adopting it:

• Nice searchable documentation to refer to future users
• Increase the amount of documentation inside the code for future contributors

https://github.com/ocsigen/tyxml

Windows 10, esy V 0.6.2, running as ADMIN.

D:\CRIME\fullstack-reason>esy install
info install 0.6.2 (using esy.json)
.... fetching yarn-pkg-config@github:esy-ocaml/yarn-pkg-config#cca65f99674ed2d954d28788edeb8c57fada5ed0
.... fetching @opam/conf-libssl@archive:https://github.com/openssl/openssl/archive/OpenSSL_1_1_1d.tar.g
.... fetching @opam/multipart-form-data@github:cryptosense/mult

This may very well already work perfectly. If that's the case, we should just document it and maybe add a test. If it doesn't work, we should make it possible.

The Elm example uses nested comments as their recursive structure. They have a special helper function (lazy), but that might be because their decoders have a ne