Just released a blog post about our Code Style Guide approach.
Last week we’ve open-sourced the guide itself on GitHub.
Contributions are adoptions are more than welcome, let’s build a canonical ReasonML & ReScript code style guide together!
Just released a blog post about our Code Style Guide approach.
Last week we’ve open-sourced the guide itself on GitHub.
Contributions are adoptions are more than welcome, let’s build a canonical ReasonML & ReScript code style guide together!
Thanks for sharing this!
I’m curious why you settled on point 12 (avoid fun functions). Could you elaborate?
Hi, thanks for you interest!
We have two minor concerns, this syntax have subjectively low readability and when you refactor a function like this into a generic one you have to basically rewrite it.
The major reason that made us include this point into the code style is that this syntax is getting deprecated in BuckleScript 8 (https://rescript-lang.org/docs/manual/v8.0.0/migrate-from-bucklescript-reason)