This repository has been archived by the owner on Apr 21, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 16
Sync with reactjs.org @ e3073b03 #205
Open
react-translations-bot
wants to merge
405
commits into
main
Choose a base branch
from
sync-e3073b03
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
Co-authored-by: Sebastian Silbermann <[email protected]>
Found an additional comma typo when I implemented this example with typescript.
Update broken link for Colorable in Color contrast section
…#4754) Co-authored-by: Romain Bohdanowicz <[email protected]>
Docs for React Router 6.4+ have moved from the "remixing" to "dev" branch.
* fix typo * Update you-might-not-need-an-effect.md * Update you-might-not-need-an-effect.md
Fixes #4770
* Hook FAQ: Change usePrevious recommendation * typo
* [Beta] Discourage derived state more * reword
* fixes empty messages added in console * Revert "fixes empty messages added in console" This reverts commit c978a82be60a55c0dd81cc9ed8ecf31d43d52385. * add min height
* fix typo in passing-data-deeply-with-context.md * Fix: typo
React Knowledgeable website seems to go to some spam website now and the community facebook page has been updated since 2019. Probably no longer active https://www.facebook.com/reactknowledgeable/
* fix: api reference links in content * fix: link on react dom api page
* Fix typo: New Zealand in travel plan example * Fix multiple typos of New Zealand in examples
* React Brussels Hybrid 2022 * React Advanced London 2022
Co-authored-by: Aimen Ben Amor <[email protected]>
…#5093) * Update 3 files * Delete console-issue.md * Filter out console error addendum Co-authored-by: dan <[email protected]>
* style: prettier according to repo rules 💅 * fix: typo
* build: ignore markdown files in content * Update .prettierignore Co-authored-by: dan <[email protected]>
* [beta] Update CodeStep colors * Add back green
* Use named React imports * More manual edits * Remove displayNames * rm dead code
* [Beta] Upgrade React/Next * useEvent * ts
This reverts commit c865f07fde583c0995d790ebbeac0c2cfaaf2707.
This reverts commit 807116a60263944604b625d323a8a51f3d3a50fd.
* [Beta] MDX 2 * Fix up old pages
Added info about RenderATL 2023
Deployment failed with the following error:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 reactjs.org at e3073b0
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.