* Memo: Document behavior with useContext
It is not obvious that useContext and Memo work well together. Namely, if a child component listens to a context and updates out from under them memo'd function, does the memo'd component have the right state if re-rendered?
yes, actually. but this is undocumented. Now it's not!
* fix typo tigger -> trigger
* Add more detail to all relevant pages
Co-authored-by: Alex Krolick <alexkrolick@users.noreply.github.com>
Co-authored-by: Sophie Alpert <git@sophiebits.com>
* Add 'visual components' use case for forwarding refs
* Rearrange "forwarding refs" to focus on simple use case
* Minor wording nits to 2018-03-29-react-v-16-3.md
* Minor wording nits to forwarding-refs.md
* Add more info to the forwardRef reference doc
* Minor wording nits to reference-react.md
Maybe I'm somehow weird, but I lived for some time with an idea that `React.Component` does implement `shouldComponentUpdate` with deep comparison. `React.PureComponent` is faster because it compares shallowly.
The changes I propose should avoid this "implicit" kind of way of thinking, since it would explicitly state that `React.Component` does not compare anything.
Hi guys,
I was reading docs on `React.Children.only()` method and saw this statement `Otherwise this method throws.` and it seemed a bit unclear for me what it supposed to throw.
Please let me know if this PR makes sense.
Thank you!
