* 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
* 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
* 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.
* 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
* 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
* Add onToggle event to details tag
Fixes#8761
* Map onToggle event on ReactDOMFiberComponent
* Tweak doc
* Trap events on setInitialProperties for details tag
* 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
* 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
Johan TinglöfandBrandon Dail
Bernard LinandBrandon Dail
Dan AbramovandGitHub
CodinCatandDan Abramov
Andrew Clark
Jamison DanceandBrandon Dail
AdamandDan Abramov
Dima BeznosandBrandon Dail
Sunny RipertandBrandon Dail
Vesa LaaksoandDan Abramov
Bryan BraunandKevin Lacker
Fokke ZandbergenandBrandon Dail
Dai NguyenandBrandon Dail
StephieandDan Abramov
Roman MatusevichandDan Abramov
DanZeussandDan Abramov
Sean GranseeandBrandon Dail
BDav24andDan Abramov
JiminikizandBrian Vaughn
Prayag VermaandDan Abramov
Moacir RosaandDan Abramov
Dhyey ThakoreandKevin Lacker
Andrew ClarkandGitHub
KBandDan Abramov
Dmitry Zhuravlev-NevskyandGitHub
Diego MuraccioleandDan Abramov
Pontus AbrahamssonandDan Abramov
Omid HezavehandDan Abramov
EduardandKevin Lacker
Tiago FernandezandKevin Lacker
Jeffrey WanandKevin Lacker
John LonganeckerandKevin Lacker
Vladimir KovpakandBrandon Dail
Senin RomanandBrandon Dail
MICHAEL JACKSONandDan Abramov
Mitchel HumpherysandBrandon Dail
ScottandDan Abramov
Oscar BolmstenandDan Abramov
Keyan ZhangandDan Abramov
mguidottoandDan Abramov