New react docs (only content) #96
Conversation
|
|
||
| ## Rules of Hooks | ||
|
|
||
| Hooks are just simple functions, but you need to follow _two rules_ when using them. ReScript doesn't enforce those rules within the compiler, so if you really want to enforce correct hooks conventions, you can use an [eslint-plugin](https://www.npmjs.com/package/eslint-plugin-react-hooks) to check your compiled JS output. |
There was a problem hiding this comment.
I'm just doing this (eslint the compiled JS output) and wondering whether it's the right way!
|
Excellent work thus far! |
|
@ryyppy is there an opportunity to assist with this task? I'd love to point my team at one place for all our rescript / react docs, so I'd love to roll up my sleeves and assist. It's a little unclear to me what the outstanding tasks are, if you could briefly point me in the right direction so I'm not stepping on your toes, I'll get to work! :D |
|
Hey @bdunn313! The The planned release will be end of January, so hopefully it will not be long until launch! |
|
Thanks for all the work on this @ryyppy.
Is there a link that references the changes you're referring to above? |
Not yet, Ricky and I are currently writing things up so we can discuss it with the community to address any edge cases for an easy migration |
ryyppy
force-pushed
the
new-react-docs-only
branch
from
40d51cb
to
f52de03
Compare
|
I will merge this now to get the ball rolling |
|
This is a great birthday present (31st)! It begins! 🥳 |
I created this branch as a replacement for #60 to be able to iterate on the React content independently from the website infrastructure. Turned out writing content for React is a long process, and I still want to work on other parts of the website :-)
Within this long running PR, only touch following files: