This repository has been archived by the owner on Apr 21, 2023. It is now read-only.
Sync with reactjs.org @ 32e3c7a6 #85
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Link each mention of a React API in rendering-elements.md to the reference docs. On this page replace every static occurrence of `ReactDOM.render()` by link to the reference docs [`ReactDOM.render()`](/docs/react-dom.html#render) Is this in the right direction @sophiebits ? 🤔 ref #2630
…Mode (#2810) This landed in 16.13 via facebook/react#17942
`<renderer>.update()` doesn't return anything
Think of "myriad" as a number. You wouldn't say "a nine of things", you would say "nine things".
1- Added getDerivedStateFromError lifecycle method to "Do Hooks cover all use cases for classes?" 2- Added getSnapshotBeforeUpdate lifecycle method to "How do lifecycle methods correspond to Hooks?"
* added stackblitz to playground * modified link of Stackblitz I changed the link based on comment from @EricSimons
This reverts commit 869c740.
adding next section URL path at the end in order to ease readers follow steps
adding the next section path at the end.
Clarifying a useState sentence
* Fix typo in hooks-faq.md * Update hooks-faq.md * Update hooks-faq.md Co-authored-by: Sophie Alpert <[email protected]> Co-authored-by: Sunil Pai <[email protected]>
- correcting assertion mistakes
`MySlowList` "lag behind" => `MySlowList` "lags behind"
* Update components docs for functional components * Update components-and-props.md Co-authored-by: Sunil Pai <[email protected]>
"You can use in new code" => "You can use them in new code"
Missing code
According to [ProofreadNOW](https://www.proofreadnow.com/blog/bid/101485/If-I-Were-or-If-I-Was-Which-is-Correct), > Guideline: Use were (instead of was) in statements that are contrary to fact.
Co-authored-by: Juan Manuel Rinaudo <[email protected]> Co-authored-by: Sunil Pai <[email protected]>
I believe it was meant to be "news story", but I could be misunderstanding something in the context of the paragraph.
* Update legacy lifecycle methods componentWillReceiveProps -> componentDidUpdate * Update legacy lifecycle methods componentWillReceiveProps -> componentDidUpdate * Update higher-order-components.md Co-authored-by: Sunil Pai <[email protected]>
* Update README.md (improve usability) Clear up the ambiguous "Running locally" to the anchor link for better usability * Update README.md Co-authored-by: Sunil Pai <[email protected]>
* Update blog post for RC1 * Update 2020-08-10-react-v17-rc.md
Disclaimer: I'm an organiser of React Summit, React Advanced London and React Day Berlin - changes proposed in this PR is a small effort to actualise the list of events next to updating our own event dates Next to updating own conference dates, I've made following changes: * Removed 2020 events that, based on the current information from their websites, are cancelled or postponed without a new date * Moved 2020 events that have actually ran to the "past events" section * Updated dates of some events in 2020 that have not announced their cancellation, but moved dates within this year What I didn't do: * I haven't added 2020 cancelled events with their assumed 2021 dates, as it's up to organizers to confirm those and re-add * To stay consistent with point above - I'm also not adding our (GitNation - React Summit, React Advanced) cancelled event dates that moved to 2021 * Conferences that have a past dates, but has not clear statement on the website about cancellation have not been removed, but rather moved to "past events" section The information is relevant as of today's date - during these hard times plans do change frequently, so some information may be outdated by the time this PR is merged. I'll be happy to provide amends until it's merged.
…… (#3159) * Updating the docs to reflect the fact that React.memo can be used with both class and functional components * removed misleading para
* Fix Navbar covering heading while using anchor in docs * reduced number of lines of code from 2 to 1 * Forgot to do tests before. Have done those now with no errors
Co-authored-by: Sebastian Silbermann <[email protected]>
* React v17.0 Release Candidate: Support for New JSX Transform * Change date and slight edits * tweak note * more thanks * fix example * Include version for TS * Add a note on running the codemod * Move and add note Co-authored-by: Dan Abramov <[email protected]> Co-authored-by: Dan Abramov <[email protected]>
Co-authored-by: Ricky <[email protected]>
|
Deploy preview for ta-reactjs ready! Built with commit 97a4137 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was automatically generated.
Merge changes from reactjs.org at 32e3c7a
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.