Sync with react.dev @ 5138e605 #753
Open
Conversation
This file contains hidden or 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
Co-authored-by: Sebastian Silbermann <[email protected]>
…(#7108) * Emphasize the second problem acapit with chain of effects example * Replace 'One' with 'First' to keep problems counting consistent
PR to add Radv 2024 conference
Co-authored-by: Tom Eastman <[email protected]>
* Update conferences.md, add conference * Update conferences.md --------- Co-authored-by: Eli White <[email protected]>
…… (#6691) * Changed the documentation of the subscribe argument to a more accurate one. * Update useSyncExternalStore.md --------- Co-authored-by: Sophie Alpert <[email protected]>
reactjsday 2024 React conference in Verona, Italy
* Fix typos in thinking-in-react.md * Update src/content/learn/thinking-in-react.md --------- Co-authored-by: Ricky <[email protected]>
…r <style> when using the `precedence` property (#7643)
This is the exact same fix as #6422 as the example is duplicated between the useOptimistic and <form> pages.
* Update index.md Invalid link to bluesky account * Update index.md Fixed invalid bluesky link for react.dev
Ports over the fix in the facebook/react repo for this workflow. We don't have to wait for it to be labeled first, now that we have the reusable maintainer check.
Defaults permissions to none for all workflows, and only request extra permissions when needed. Similar to facebook/react#32708, prefer the less permissive `pull_request` trigger instead.
* [ci] Fix permissions and don't use pull_request_target Defaults permissions to none for all workflows, and only request extra permissions when needed. Similar to facebook/react#32708, prefer the less permissive `pull_request` trigger instead. * [ci] Pin 3rd party actions to specific hash
facebook/react#32727 removes the `is_remote` param.
* Add React Prague community * Update link
* Remove captureOwnerStack canary banner * Update nav and site config
* update reactrouter url * Update src/content/learn/build-a-react-app-from-scratch.md --------- Co-authored-by: Ricky <[email protected]>
1. Stop using `canary` for `captureOwnerStack` sandboxes 1. Remove remaining Canary badges from `captureOwnerStack` mentions
Updated `react-ahmedabad` community link to respective domain name
Co-authored-by: Rick Hanlon <[email protected]>
… (#7682) * Fix small grammatical mistake * Update src/content/learn/reusing-logic-with-custom-hooks.md --------- Co-authored-by: Ricky <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
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 5138e60
The following files have conflicts and may need new translations:
Please fix the conflicts by pushing new commits to this pull request, either by editing the files directly on GitHub or by checking out this branch.
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.