A while ago I published this article about building an accessible and reusable modal/dialog component in React.
React modal
The component ach...
For further actions, you may consider blocking this person and/or reporting abuse
Thanks for the amazing article! Very useful practical info on how to implement tricky things in ReasonReact.
Just wanted to mention,
keyCodeis being deprecated according to MDN docs, instead it seems like key property is a safer choice in this case.Thanks! I'll correct that.
Hey Seif, nice article. Just fyi there is a recommended community binding to the Web API: github.com/reasonml-community/bs-w...
Nice series so far 👍 Now I have to introduce you to Mint (which I am the author of) - a language which uses React as a platform (same as Reason) and have the same semi functional approach. I have a feeling you will like it 😉
Lack of documentation is a ship stopper. Thats why Reason is a no-go area for now.
The lack of documentation surrounding Reason, Reason React, and the whole Reason / OCaml ecosystem is definitely a bummer.
It's no substitution, but Reason and OCaml code both tend to be extremely self documenting if you dive into the source code, due to the strong typing and interface files.
I'm hoping that this is an issue that can start to be solved because Reason and OCaml are both great, but without proper documentation it will be struggle to get people to adopt them in their projects.
It's also the fact that there as so few threads in Stackoverflow and Reddit. I don't even see people writing about it. Just sporadically.
I feel you, there are definitely certain gaps in the documentation. I think it's still very good documentation though. I can say that because I managed to write this series just by reading Reason & ReasonReact documentation. During the few times where I got stuck, the community on the forums & Discord was immediately helpful.