-
Notifications
You must be signed in to change notification settings - Fork 182
Sync original #91
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Sync original #91
Conversation
* add warning for invalid hook call * Fix versions * Split code examples * unnecessary comma * tweaks * Update content/warnings/invalid-hook-call-warning.md Co-Authored-By: gaearon <dan.abramov@gmail.com> * nit
This reverts commit e301239.
…into gaearon-hooks-stable
Update docs for stable Hooks
* react-testing-library now supports `act` * fix typo
Support Custom-ID Markdown Syntax
Wow, I was anticipating something very tedious, but there are only four conflicts and all of them are fairly easy to resolve :) So should I directly push to this branch to resolve conflicts? |
Haha, the spanish fork translated more hooks articles so they have more conflicts :P Just direct push to the branch! |
Done! Actually this merge has changes that involve several ongoing PRs, but I'll take care of notifying the translators. |
@smikitky I think it shouldn't squash-merge. it should keep the original commits. |
Okay, I re-enabled merge commits. |
@koba04 Could you approve? We should merge this PR before @takanorip and I can update the corresponding PRs. |
@smikitky OK, I'll review this soon 🚀 |
done |
Doing this manually since there's a ton of commits.
The only page that has interfering translations is
hooks-intro.md
. It seems like thegit merge
is pretty smart about only creating a conflict where the english text has changed!https://github.com/reactjs/ja.reactjs.org/pull/91/files#diff-daed9eb3a7702fb9fe0397b0f613d4faL8