Sync with react.dev @ b12743c3 #69
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
`an text area` -> `a text area` `an discussion` -> `a discussion`
…6728) Signed-off-by: Faridul Islam <[email protected]>
Noticed this randomly and couldn't unsee it, so here's a quick PR to fix.
* change isOpen variable in TopNav component to isMenuOpen to differentiate from isOpen props in Search component change setIsOpen to setIsMenuOpen in TopNav component * move initialization of ShowSearch state to top-level of TopNav component organize hook initializations in TopNav component: useState, useRef, useRouter * remove initialYScroll prop from DocSearchModal component to fix search functionality on ios devices
* Add docs for onCaughtError and onUncaughtError * Updates from feedback
Note that this component is not actually expandable and the ref got likely unused when that was removed
* in \[errorCode\].tsx, wrapped parsedContent in a div and applied styling of white-space: pre-wrap to preserve whitespace and break on newline chars * updated styling to tailwind class
Tickets are sold out, update the text.
* API docs for useDeferredValue's initialValue Updates the API docs for `useDeferredValue` to include the `initialValue` option, added in facebook/react#27500. This feature is slated for release in React 19. * Add docs for onCaughtError and onUncaughtError (#6742) * Add docs for onCaughtError and onUncaughtError * Updates from feedback * Add canary info, simplify a bit --------- Co-authored-by: Ricky <[email protected]>
* Add documentation for ref cleanup functions * Contain changes within canary block
* move useFormState api * add redirect * use React DOM as the name
* Blog posts for React 19 * Feedback * Feedback * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Josh Story <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Noah Lemen <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Matt Carroll <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Matt Carroll <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Noah Lemen <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Noah Lemen <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Noah Lemen <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Noah Lemen <[email protected]> * Update src/content/blog/2024/04/25/react-19.md * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Matt Carroll <[email protected]> * Thanks * Apply suggestions from code review Co-authored-by: Matt Carroll <[email protected]> Co-authored-by: Sebastian Silbermann <[email protected]> * Feedback * nit * Issue link --------- Co-authored-by: Josh Story <[email protected]> Co-authored-by: Noah Lemen <[email protected]> Co-authored-by: Matt Carroll <[email protected]> Co-authored-by: Sebastian Silbermann <[email protected]>
* Typos in React 19 * Headings
should assign the result of updateName Co-authored-by: Tim Neutkens <[email protected]>
* Make use(Context) example easier to understand * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Ricky <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Ricky <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Ricky <[email protected]> * Update src/content/blog/2024/04/25/react-19.md Co-authored-by: Ricky <[email protected]> --------- Co-authored-by: Ricky <[email protected]>
…s stable but the packages you work with as a framework and bundler will approach API stability (#6782)
Using "off", "warn", "error" has been supported for many years now - I think this helps improve the readability :) I completely forgot what rule: 2 meant - had to find it at https://eslint.org/docs/latest/use/configure/rules
Removed ; as it's unnecessary in jsx component
Front end nation is covering a full track of React talks including speakers such as: * Kent C Dodds * Sara Vieira * Tejas Kumar
Co-authored-by: OH HYUN KEUN <[email protected]>
This upstreams some of the [introduction post](reactwg/react-compiler#5) into the docs since this knowledge is quite fundamental to understanding the compiler, and it's confusing to not have it linked in the canonical source for the docs. It also adds more information about [debugging](reactwg/react-compiler#7) and reorganizes a few sections to make things clearer ghstack-source-id: ef32fc723722eb5119529abcc572dd2bcf2b1cab Pull Request resolved: reactjs/react.dev#6895
* Add React Conf 2024 Recap post * Spelling and links * Apply suggestions from code review Co-authored-by: lauren <[email protected]> * Edits * Edits * better link * Update date * Update date and nits * feedback --------- Co-authored-by: lauren <[email protected]>
* Add codemods to upgrade guide * Update src/content/blog/2024/04/25/react-19-upgrade-guide.md Co-authored-by: Ahmed Abdelbaset <[email protected]> * Add benefits --------- Co-authored-by: Ahmed Abdelbaset <[email protected]>
The docs for stylesheet precedence incorrectly state that there is an enumerated set of valid precedences. This is incorrect. The precedence value can be anything and React infers the hierarchy from the order in which it discovers precedences
* FIX: Typo in useEffect.md caveats * Fix another typo
* Add act documentation * Update structure based on feedback * Add usage examples and async act --------- Co-authored-by: Rick Hanlon <[email protected]>
react-translations-bot
force-pushed
the
sync-b12743c3
branch
from
7308078
to
616b970
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was automatically generated.
Merge changes from react.dev at b12743c
DO NOT SQUASH MERGE THIS PULL REQUEST!
Doing so will "erase" the commits from main and cause them to show up as conflicts the next time we merge.