Sync with react.dev @ b12743c3 #272
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
* Upgrade react-collapsed * 4.0.4 --------- Co-authored-by: Rogin Farrer <rfarrer@wayfair.com>
Added new meetup in Saskatoon - SK
Co-authored-by: Luna Wei <luwe@fb.com>
* fix: add a missing import statement in useFormStatus.md * Update src/content/reference/react-dom/hooks/useFormStatus.md Co-authored-by: Ahmed Abdelbaset <A7med3bdulBaset@gmail.com> --------- Co-authored-by: Ahmed Abdelbaset <A7med3bdulBaset@gmail.com>
Co-authored-by: Luna Wei <luwe@fb.com>
* Cleanup old ga-lite tag and refactor GA4 * cleanup * cleanup2
* Add Error Boundary to useTransition docs * add Error Boundary to useTransition * Use Canary * Add Error Boundary to useTransition API docs * Update src/components/MDX/Sandpack/Preview.tsx Co-authored-by: Jan Kassens <jan@kassens.net> * Update src/content/reference/react/useTransition.md Co-authored-by: Luna <lunaleaps@gmail.com> * Update src/content/reference/react/useTransition.md Co-authored-by: Luna <lunaleaps@gmail.com> * Add Error Boundary to useTransition docs * add Error Boundary to useTransition * Use Canary * Add Error Boundary to useTransition API docs * Update src/components/MDX/Sandpack/Preview.tsx Co-authored-by: Jan Kassens <jan@kassens.net> * Update src/content/reference/react/useTransition.md Co-authored-by: Luna <lunaleaps@gmail.com> * Update src/content/reference/react/useTransition.md Co-authored-by: Luna <lunaleaps@gmail.com> * Address comments and update usage example * Address comments and update usage example * Update src/content/reference/react/useTransition.md Co-authored-by: Luna <lunaleaps@gmail.com> --------- Co-authored-by: Jan Kassens <jan@kassens.net> Co-authored-by: Luna <lunaleaps@gmail.com>
* Warn about low entropy in taintUniqueValue.md * Update src/content/reference/react/experimental_taintUniqueValue.md Co-authored-by: Jan Kassens <jan@kassens.net> --------- Co-authored-by: Jan Kassens <jan@kassens.net>
Add useFormState reference
* Add useFormState reference * Matt's suggestions for useFormState reference * Incorporated PR feedback for useFormState
Co-authored-by: Nikhil Gupta <nikhil.gupta5667@gmai.com>
Co-authored-by: Luna <lunaleaps@gmail.com>
* Add useOptimistic API reference documentation * Fix title * Add working exmaple from form and updadd parameters * Add updates to useOptimistic * Add updates to useOptimistic * Add updates to useOptimistic --------- Co-authored-by: Matt Carroll <mattca@meta.com>
Google uses this on many of our API doc pages and it's not a good snippet. Only put this on the homepage but leave the og:description and twitter:description.
* Adds landing page for reference section.) * Updated hyperlinks. * Fixes Legacy APIs link. * Removes canary image from heading.
Co-authored-by: Sophie Alpert <git@sophiebits.com> Co-authored-by: Luna Wei <luwe@fb.com>
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 <ohhk@uitgis.com>
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 <poteto@users.noreply.github.com> * Edits * Edits * better link * Update date * Update date and nits * feedback --------- Co-authored-by: lauren <poteto@users.noreply.github.com>
* Add codemods to upgrade guide * Update src/content/blog/2024/04/25/react-19-upgrade-guide.md Co-authored-by: Ahmed Abdelbaset <A7med3bdulBaset@gmail.com> * Add benefits --------- Co-authored-by: Ahmed Abdelbaset <A7med3bdulBaset@gmail.com>
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 <rickhanlonii@fb.com>
react-translations-bot
force-pushed
the
sync-b12743c3
branch
from
5ec0c33 to
ea7a607
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.