Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync with react.dev @ 303ecae3 #380

Open
wants to merge 146 commits into
base: main
Choose a base branch
from
Open

Conversation

react-translations-bot
Copy link
Collaborator

This PR was automatically generated.

Merge changes from react.dev at 303ecae

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.

mekarthedev and others added 30 commits May 23, 2023 15:01
* Fix manipulating-the-dom-with-refs

* Update manipulating-the-dom-with-refs.md

---------

Co-authored-by: dan <dan.abramov@gmail.com>
…utilize Node.js v16 (#6084)

* Update site_lint.yml

* Update site_lint.yml
The inner component is `EditForm`, not `EditContact`.
* Add basic reference pages for use client and server

I guess this turned into a bit more of an FAQ but I think it's useful to have this written down in a canonical place.

* Oops, push final tweaks
this is the canonical link now 🫡
The "onFocus" is fired when an element receives focus, not loses.
* Fix homepage title

Fixed homepage title bug, now the homepage will display the title from `content/index.md` instead of the constant `React`.

* Update index.md

Change title to "React" to keep same
* Start of the typescript page

* Intro

* Intro

* Use State

* Use Reducer

* Start of context

* Use Ref

* Events

* Wrap up 1st draft

* Better titles

* Apply suggestions from code review

Co-authored-by: Tom Sherman <the.tomsherman@gmail.com>
Co-authored-by: Lenz Weber-Tronic <mail@lenzw.de>

* Note types/react and types/react-dom, and tone down the usecontext null check

* Feedback

* Given a 2nd run through of the doc

* Apply suggestions from code review

Co-authored-by: Ricky <rickhanlonii@gmail.com>

* Document where `State` is coming from

* Link what inferred types are

* Remove "knock-on"

We already say "cause" which makes "knock-on" a bit redundant

* Move useRef TS usage to useRef reference page

dropped useEffect since there's nothing specific about this hook.

* Add installation section

* Link to framework specific guides

* Edits

* Edit footer

* Rm useRef docs

---------

Co-authored-by: Tom Sherman <the.tomsherman@gmail.com>
Co-authored-by: Lenz Weber-Tronic <mail@lenzw.de>
Co-authored-by: Ricky <rickhanlonii@gmail.com>
Co-authored-by: Sebastian Silbermann <sebastian.silbermann@klarna.com>
* [WIP] Add UI for canary releases

* yellow

* Switch to icon and gray

* Wording, alignment, and rm flex

* Heading alignment
* change docs

* add docs for create react app

* remove

* Update src/content/learn/tutorial-tic-tac-toe.md

---------

Co-authored-by: Ricky <rickhanlonii@gmail.com>
smikitky and others added 29 commits November 6, 2023 14:09
Summary of changes:
"Server Action", like "Effect", is a React-specific notion
that would be benefited from captailization to be distinguished
from its genertic meaning.

It seems like [Next doc](https://nextjs.org/docs/app/api-reference/functions/server-actions)
has also adopted such connventions and we should probably do the same.

Co-authored-by: xuan.huang <xuan.huang@bytedance.com>
Summary of changes:
following <reactjs/react.dev#6417>

Co-authored-by: xuan.huang <xuan.huang@bytedance.com>
Summary of changes:
See <reactjs/react.dev#6417>

Co-authored-by: xuan.huang <xuan.huang@bytedance.com>
Co-authored-by: Luna Wei <luwe@fb.com>
Summary of changes:
See <reactjs/react.dev#6417>.

There is one exception though. The error message
“Rendered fewer hooks than expected” from React is indeed "hooks"
so I kept as-is. Shall we change the error message from React?

Co-authored-by: xuan.huang <xuan.huang@bytedance.com>
Summary of changes:
See <reactjs/react.dev#6417>

Co-authored-by: xuan.huang <xuan.huang@bytedance.com>
Summary of changes:
See <reactjs/react.dev#6417>

Co-authored-by: xuan.huang <xuan.huang@bytedance.com>
…(#6445)

* Fix: component not returned

* Fix: missing function statement
Summary of changes:
There is one "TypeScript strict mode" that is kept unchanged.

Co-authored-by: xuan.huang <xuan.huang@bytedance.com>
Co-authored-by: Sebastian Silbermann <silbermann.sebastian@gmail.com>
this way "cannot be marked" is all the same style and you don't skim the link text and gloss over the "cannot be"
* fix(sandpack-template): use custom react sandpack template

* refactor: Remove console.log statement

Remove console.log(filePath); from createFileMap.ts

* style: Update file paths in Sandpack components

Update file paths in Sandpack components to use root folder and variables
* feat: add react india 2024

* update: move react india 2024 in date order

* update: move conferences to past section

* refactor: sort past conferences
…6496)

* specify which sandbox files go in src directory

* fix some stragglers
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet