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 33
Sync with reactjs.org @ e5fd79cd #142
Open
react-translations-bot
wants to merge
145
commits into
main
Choose a base branch
from
sync-e5fd79cd
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
* Pass route lists explicitly * Inline MarkdownPage into Page * Pass breadcrumbs from above * Remove state from router utils * Pass section from above
* Remove old blog entries * Blog MVP * TS
Change "and you code" to "and your code"
* [Beta] Repsonsive iframes * Fix links
* Update past conferences chronological list * Update React India 2023 dates on beta docs * Fix conference order for past conferences 2022 * Fix failing header id lint error : ; lld ;
Fix broken link to `useDeferredValue` reference
* fix: resolved conflicts * Remove un-used file --------- Co-authored-by: Asif Vora <[email protected]>
* Remove dead prop * Use React.lazy * Render at most one dialog at a time
* Add React Labs March 2023 blog post * Remove smart quotes * Fix typo * Fix smart quote direction * edits * edits * clean up asset loading section * more edits * better summary for blogcard * Add additional context to offscreen section I expanded the Offscreen rendering section a bit to deemphasize the API itself and focus more on the high level capabilities it will unlock. Since 1) it's unlikely <Offscreen> is the final API 2) most React developers will not use it directly. * Tweak to sentence in offscreen section * fix minor typo * edits * merge * upd * oops * twk * Update src/content/blog/2023/03/22/react-labs-what-we-have-been-working-on-march-2023.md Co-authored-by: lauren <[email protected]> * Update src/content/blog/2023/03/22/react-labs-what-we-have-been-working-on-march-2023.md Co-authored-by: lauren <[email protected]> * oops * edits * edits * ok --------- Co-authored-by: Andrew Clark <[email protected]> Co-authored-by: Dan Abramov <[email protected]>
…(#5807) We use "top level" all over the docs, but this specific topic uses a different meaning of "level". If you're learning about passing context across multiple "levels" of components, this is actually pretty confusing and makes you think you can only useContext at, for example, the top level of your app.
* Resolved the CSS conflict * Resolved the CSS conflicts in other files
'Your Effect would look like similar to this' -> 'Your Effect would look similar to this'
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 e5fd79c
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.