Please sign in to comment.
Added more info about refs in the documentation (#8707)
* Update refs-and-the-dom.md I want to propose some changes to the Refs and the DOM documentation page. - Make it clear that string refs are legacy. It seems that this information got lost during the transition to new docs and only some part stayed the same, which was confusing when first reading the docs. - Clarify and explain that during render, if the ref callback is provided, it will get called twice, first with `null` and then with the rendered DOM element. Discussed in #4533 and first proposed docs change in PR #8333. I've also planned on adding an example for passing the refs up the component chain based on something I've needed to solve myself (e.g. you want to connect two dynamic components by line in React, so you need to both use refs and propagate them up the chain), and while it would be great to read up on this in the docs, it may be too specific for this section; I'd be happy to hear any recommendations. * Adds more specific information about the callback * Moved the ref callback description to the Caveats section * Fixed suggested nits * Replace 'each render pass' with 'updates' * Tweak the wording
- Loading branch information...