features → feature
> There is nothing "bad" about using state or lifecycle hooks in components. Like any powerful feature**s**, they should be used in moderation, but we have no intention to remove them.
I can’t explain the exact grammatical principle this violates, but it sounds wrong to my native English ears that “feature” is plural here. Another way to check if the grammar sounds right is to change the order of the clauses: ”They should be used in moderation, like any powerful feature“ sounds right, whereas “They should be used in moderation, like any powerful features” does not.
* Updated Chain React
Changed conference date from "Summer 2017" to given date on website
* Updated React Native EU
Updated date and place with information from website
(cherry picked from commit 2b59afb984)
* Update Lifting State Up not to mix up DOM value with component state
A few weeks ago when teaching my friend, she got stuck on
`this.state.value` vs. `event.target.value`. As the documentation
talked a lot about "values", and the term value could mean three
different things (values in general, the "value" prop / DOM value of
the <input> component and the value in state/props), it was not weird
that she got a bit confused.
* Rename Lifting State Up onChange props to onTemperatureChange
This is in-line with how the temperature is provided as a prop named `temperature`
* Fix one value prop not being renamed to temperature
* Update codepen examples in Lifting state up documentation
* Update devtools state change to reflect docs change
(cherry picked from commit a190cfce29)
* Replace the header_links plugin with client-side generated anchors.
Fixesfacebook/react#4124
* Move anchor-link code into a separate script
Also adds a couple comments, for context.
(cherry picked from commit 7a878d27e3)
* Improved for a better understanding
that code shouldn't name this parameter onchange. It is so confusing for a starter of ReactJs like me. It looks like that the onChange is an common event from props.
* Update the lifting state up paragraph
I tried to write something to explain to starter programmers in react, how we lift the state up calling a method defined by the ancestor and called by the children that will affect the children element.
* Rewrite Lifting State Up
(cherry picked from commit fc362bf095)
* Add note about refs on stateless components
* Move info about refs in the stateless components to the main section
* Simplification of the part about refs and functional components
* Tweaks
* Move sections around
* Oops
* Rearrange more sections
(cherry picked from commit d42c285aa2)
* Explain arbitrariness of ref name in callback
The sample code was confusing because it's not clear that "textInput" in this.textInput is an arbitrary name for the ref.
* Tweak wording
(cherry picked from commit 79be3543dd)
* Add benchmarking tutorial
I've written what I hope is the simplest introduction to benchmarking React components. It's meant to be straightforward and easy to follow for beginners. If you agree that it would be helpful, I'd like to add it to the docs.
Would also welcome any and all feedback.
* Just put links together
(cherry picked from commit 4c6fec902f)
* Added a link to "State Updates are Merged"
* better inline links
* moved the explanation down
* Minor unrelated tweaks
(cherry picked from commit eb89bc4c30)
* Update conferences.md
* Update conferences.md
path fixed
* Changed capitalization to match the website and Twitter
(cherry picked from commit b2b6d9daf7)
* Reminder: strip quotes from attributes with JS code
Web developers who are used to standards-compliant HTML and XML will, out of habit, put quotes around all attributes because the standards require them. Other templating systems like ASP.NET also require (or at least allow) quotes around attributes that contain code. This behavior will get users into trouble in JSX because a quoted attribute is always treated as a string literal, even if it contains curly-braced javascript code. Let's add to the docs to help newbies evade this problem.
* Tweak wording
(cherry picked from commit fc302494b7)
Aaron CannonandAndrew Clark
JustinandAndrew Clark
Dan AbramovandAndrew Clark
Johan TinglöfandBrandon Dail
Bernard LinandBrandon Dail
CodinCatandBrandon Dail
Jamison DanceandBrandon Dail
Andrew ClarkandBrandon Dail
AdamandDan Abramov
Dima BeznosandDan Abramov
Sunny RipertandDan Abramov
Vesa LaaksoandDan Abramov
Bryan BraunandDan Abramov
Fokke ZandbergenandDan Abramov
Dai NguyenandDan Abramov
StephieandDan Abramov
Roman MatusevichandDan Abramov
DanZeussandDan Abramov
JiminikizandDan Abramov
Prayag VermaandDan Abramov
Moacir RosaandDan Abramov
Dhyey ThakoreandDan Abramov
KBandDan Abramov
Pontus AbrahamssonandDan Abramov
Omid HezavehandDan Abramov
EduardandDan Abramov
Tiago FernandezandDan Abramov
Jeffrey WanandDan Abramov
John LonganeckerandDan Abramov
Vladimir KovpakandDan Abramov
Senin RomanandDan Abramov
MICHAEL JACKSONandDan Abramov
Mitchel HumpherysandDan Abramov
ScottandDan Abramov
Oscar BolmstenandDan Abramov
Keyan ZhangandDan Abramov
mguidottoandDan Abramov
Justin GrantandDan Abramov
Ragnar Þór ValgeirssonandDan Abramov
SunHuaweiandDan Abramov