Sync with react.dev @ 2da4f7fb #125
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
* Fix view transition example * Empty commit * Fix fullscreen example
* Update useEffectEvent docs for canary * Clean up prefixed imports * Fix import * Update blog post link
* Docs for `cacheSignal` * Apply suggestion from review Co-authored-by: Sebastian Markbåge <sebastian@calyptus.eu> * Apply suggestion from review Co-authored-by: Sebastian Markbåge <sebastian@calyptus.eu> * Update src/content/reference/react/cacheSignal.md --------- Co-authored-by: Sebastian Markbåge <sebastian@calyptus.eu>
* docs: scaffold docs structure for Performance tracks * docs: initial draft of Tracks section * refactor: moved to reference root section and added to the sidebar * chore: updated to canary and minor changes
* Init PPR docs * Overhaul * Apply suggestions from code review --------- Co-authored-by: Sebastian Sebbie Silbermann <sebastian.silbermann@vercel.com>
* wip * feedback and rm canary stuff * tweak * fix json * more canary stuff * fix link * update dates * update meta description * Expand performance track section * adjust linter note * edit perf tracks down * edit perf tracks down more * tweak note * tweak useEffectEvent * formatting * tweaks * ppr * rm canary stuff * fix json * fix json * tweaks * linter note * nit * nit * link * nit * ppr * missing await * add lint v6 * fix link --------- Co-authored-by: Dan Abramov <dan.abramov@gmail.com>
We're updating eslint-plugin-react-hooks with support for useEffectEvent usage and updated configuration options for applying the useEffectEvent and other effect rules to custom effect hooks. This adds the documentation for the config syntax and adds mention to the useEffectEvent reference page that the linter should be used to ensure proper usage of Effect Events.
* Fix Activity sandboxes * hacky fix
* Use stable release in demos with HTML output * Fix Activity sandboxes (#8035) * Fix Activity sandboxes * hacky fix * Revert "Fix Activity sandboxes (#8035)" This reverts commit f9fd07c. * Bump to 19.2 * cleanup rest of sandpacks * Pin deps * Add back package.json with third-party deps * "^" should be fixed now * add back package.json for more toastify deps * fuggin whitespace * more fuggin whitespace * fml like fr fr --------- Co-authored-by: Sebastian Sebbie Silbermann <sebastian.silbermann@vercel.com> Co-authored-by: Ricky <rickhanlonii@gmail.com> Co-authored-by: Rick Hanlon <rickhanlonii@meta.com>
* Add experimental docs for Fragment refs * Update wording * Address feedback
Updates all mentions of eslint-plugin-react-hooks rc and 6.1.0 to refer to the new 6.1.1 which has important bugfixes.
Updated description of eslint-plugin-react-hooks configuration and preset.
Upgrade to latest
Updates our blog posts and docs for React Compiler 1.0
* fix: correct link for RedwoodJS to RedwoodSDK in documentation * fix: update links for React Query and TanStack Start in documentation * fix: update Vite installation command to use TypeScript template * fix: update references from React Query to TanStack Query in documentation
Fixes #8097 The refactored example in the "Chains of computations" section uses an incorrect condition that changes the game logic from the original. The original Effect-based code advances the round after 4 gold cards: - Increments first (0→1, 1→2, 2→3, 3→4) - Then checks `goldCardCount > 3` (true when count is 4) The refactored code with `goldCardCount <= 3` allows 5 gold cards: - Checks before incrementing - Allows counts 0, 1, 2, 3 to increment (4 values) - Advances on the 5th card (when count is 4) This fix changes the condition to `goldCardCount < 3`: - Allows counts 0, 1, 2 to increment (3 values) - Advances on the 4th card (when count is 3) - Matches the original behavior Verified by tracing execution logic and building the docs site locally. Co-authored-by: PaulyBearCoding <PaulyBearCoding@users.noreply.github.com>
…ave-dev` to `—save-dev`) (#8146) * Skip smartypants on TerminalBlock * Improve TerminalBlock HTML tags * Remove unnecessary TerminalBlock escapes from docs * Bump DISK_CACHE_BREAKER
react-translations-bot
force-pushed
the
sync-2da4f7fb
branch
from
9eccefa to
9737fb5
Compare
react-translations-bot
force-pushed
the
sync-2da4f7fb
branch
from
9737fb5 to
3a72d58
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
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 2da4f7f
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.