Skip to content

Sync with reactjs.org @ 2ef0ee1e #199

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

Merged
merged 31 commits into from
Mar 23, 2020
Merged

Sync with reactjs.org @ 2ef0ee1e #199

merged 31 commits into from
Mar 23, 2020

Conversation

reactjs-translation-bot
Copy link
Contributor

@reactjs-translation-bot reactjs-translation-bot commented Mar 16, 2020

This PR was automatically generated.

Merge changes from reactjs.org at 2ef0ee1

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.

sairam and others added 22 commits March 9, 2020 15:27
was inconsistent across examples
* remove a reference to fbjs from codebase overview

* Update codebase-overview.md

Co-authored-by: Sunil Pai <[email protected]>
We shouldn't be encouraging this pattern which requires good understanding of JS quirks and can lead to bugs in other instances.
Added MyContext for clarity.
Removed unused props for clarity.
The ternary syntax using parenthesis was an unconventional prettier invention, going out of its way to format react ternaries differently from normal ternaries (if i remember correctly, because vim users had trouble re-formating without a mouse). If they made the right decision or not is one thing, but the additional noise could mislead beginners here, thinking they have to add more characters to make a simple 2-slot ternary, or that it is a "react thing".
* Minor grammar edit (syntactic -> syntactical).

* Update handling-events.md

Co-authored-by: Sunil Pai <[email protected]>
* Clarify preferred "props default to true" expr

The current text is ambiguous without reading further into the paragraph -- until I re-read this text, I was trying to avoid both types of syntax because it seemed to imply that it wans't recommended (eg "props default to true" --> "we don't recommend using this").

* Update jsx-in-depth.md

Co-authored-by: Sunil Pai <[email protected]>
* Make React.memo documentation more clear

* Update reference-react.md

Co-authored-by: Sunil Pai <[email protected]>
* DOC: Updated the React Native Home URL

* Blog: Updated the React URL Link

* Relative link added
* Upgrade to node 12 LTS

* Run prettier
Date change for Render-Atlanta 2020 due to the Coronavirus pandemic.
Having the information that the plugin is already installed by default after the installation instructions is probably wasting a lot of people's time. Moving it up probably avoids multiple installs of the plugin.
@netlify
Copy link

netlify bot commented Mar 16, 2020

Deploy preview for tr-reactjs ready!

Built with commit d9d4c3f

https://deploy-preview-199--tr-reactjs.netlify.com

@alioguzhan alioguzhan merged commit 6a45b84 into master Mar 23, 2020
@alioguzhan alioguzhan deleted the sync-2ef0ee1e branch March 23, 2020 14:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.