-
Notifications
You must be signed in to change notification settings - Fork 182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sync with reactjs.org @ 081bb312 #264
Conversation
more unstable -> less stable
* Add app.js conf * Change spelling of Kraków
Removes a redundant "about this" in the concurrent-mode suspense docs.
Fix typo: `timeout:` to `timeoutMs:`
Fix #createblockingroot link
The variable name that's loading is called `user`
* Update tools-starter-kits.md Please consider adding Crisp React. Thank you. * Update tools-starter-kits.md Thanks for the amendment. Co-Authored-By: Alexey Pyltsyn <[email protected]>
* format post react-v16.9.0 * running yarn check-all
ReactConf just finished, so making a quick update to the upcoming conference list. 💞
We have unexpected text on the page. This PR fixes it.
s/MyShowList/MySlowList Updated to reflect actual component name in example: `<MySlowList text={text} />`
Deploy preview for ja-reactjs ready! Built with commit 1b5c85d |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
コンフリクト自体は一瞬で解決できましたが concurrent mode と prerelease 絡みの新規記事が結構増えていますので、これらは testing の時と同様に別に翻訳していく必要があります。
新しい Issue を立てましょうか、それとも #4 の利用を続けましょうか?
@smikitky |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
This PR was automatically generated.
Merge changes from reactjs.org at 081bb31
The following files have conflicts and may need new translations:
Please fix the conflicts by pushing new commits to this pull request, either by editing the files directly on GitHub or by checking out this branch.
DO NOT SQUASH MERGE THIS PULL REQUEST!
Doing so will "erase" the commits from master and cause them to show up as conflicts the next time we merge.