* [18] ReactDOM reference to createRoot/hydrateRoot (#4340
)
* [18] ReactDOM reference to createRoot/hydrateRoot
* Update note about render and hydrate
* Match the warning text
* s/Render/render
* [18] Update ReactDOMClient docs (#4468
)
* [18] Update suspense docs for unexpected fallbacks (#4500
)
* [18] Update suspense docs for unexpected fallbacks
* Add inline code block
* Feedback fixes
* [18] Updated Suspense doc with behavior during SSR and Hydration (#4484
)
* update wording
* wording
* update events
* Update content/docs/reference-react.md
Co-authored-by: Sebastian Silbermann <silbermann.sebastian@gmail.com>
* add link to selective hydration
* remove some of the implementation details
Co-authored-by: Sebastian Silbermann <silbermann.sebastian@gmail.com>
* [18] renderToPipeableStream doc (#4485
)
* new streaming ssr api
* add readable stream
* code snippets
* Rename strict effects / unsafe effects to use the reusable state terminology (#4505
)
* Add draft of 18 release post
* Add links to speaker Twitter profiles
* [18] Update upgrade guide
* Fix typo in blog title
* [18] Blog - add note for react native
* [18] Add changelog info to blog posts
* Edit Suspense for data fetching section
* Update date
* [18] Add links
* Consistent title case
* Update link to merged RFC
* [18] Update APIs and links
* [18] Add start/useTransition docs (#4479
)
* [18] Add start/useTransition docs
* Updates based on feedback
* [18] Generate heading IDs
* Add note about Strict Mode
* Just frameworks
* Reorder, fix content
* Typos
* Clarify Suspense frameworks section
* Revert lost changes that happened when I undo-ed in my editor
Co-authored-by: salazarm <salazarm@users.noreply.github.com>
Co-authored-by: Sebastian Silbermann <silbermann.sebastian@gmail.com>
Co-authored-by: Sebastian Markbåge <sebastian@calyptus.eu>
Co-authored-by: Andrew Clark <git@andrewclark.io>
Co-authored-by: dan <dan.abramov@gmail.com>
This matters for user security.
I didn't touch blog posts & pages related to past conferences.
The `content/docs` could be HTTPS-ified as well but it contains lots of HTTP
links so maybe that'd be best done in a separate PR.
`theme ? 'dark' : 'light'` will always use the dark theme no matter what it's set to in context. Guessing this is not what was intended? This PR fixes it.
* Update Ref API in docs
Update to new React.createRef() API in guide "Uncontrolled Components".
* Update Ref API in doc example
Use new Ref API in guide's example.
* Fix syntax error in example
* Update highlighting ranges in docs
After updating to the new createRef API, the highlighting ranges in Uncontrolled Components were wrong.
* Update highlighting ranges in docs example
After updating to the new createRef API, the highlighting ranges in Uncontrolled Components were wrong.
* Update highlighting ranges in docs example
Remove empty line in source code.
* Update uncontrolled-components.md
* Update input-type-file.js
* 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
* Added an example showing how to update the context from inside a (deeply) nested component
* Wrap comments
* Wrap comments
* Tweak wording
* Prettier
* Prettier
* Typo: "funtion" -> "function"
* Minor: context/theme-detailed-app.js broken
Today I tested out the new Context API using using [CRA](https://github.com/facebook/create-react-app).
I encountered a runtime exception, so this tiny PR is intended to make it easier for future Context API learners.
`ReferenceError: Must call super constructor in derived class before accessing 'this' or returning from derived constructor`
create-react-app@next commit da518d2238298dd5db74e9c63c12251099f87bb0
* Update theme-detailed-app.js
When a new `id` prop is passed in, `getDerivedStateFromProps` sets `this.state.externalData` to `null`. If I understand the new API correctly the return value of gDSFP() either becomes the new state or is merged into the new state? If so, then `componentDidUpdate` should examine the new state (`this.state.externalData`), not `prevState.externalData`.
* Use correct component name in context doc example
I'm assuming the intention was to reference the `FancyButton` component defined directly above, unless I'm misunderstanding how to read this example.
* Prettier
dan
Ricky
Niklas P
Charlie Stras
Fran Zekan
Ruslan Petrov
Sebastian Markbåge
Michał Gołębiowski-Owczarek
Alexander Nanberg
Tanyoung Kim
Nathan Quarles
Rodrigo Bermúdez Schettino
Brian Vaughn
Andrew Clark
Travis Arnold
Brian Vaughn
Lucas Duailibe
Toru Kobayashi
tjallingt
Chanyeon Kim
Tom Gallacher
Pat
Christian Maughan Tegnér