Sync with react.dev @ 943e3ce4 - #378
Closed
react-translations-bot wants to merge 134 commits into
Closed
Conversation
* 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>
* Add useOptimistic API reference documentation * Fix title * Add working exmaple from form and updadd parameters * Add updates to useOptimistic * Add updates to useOptimistic * Add updates to useOptimistic --------- Co-authored-by: Matt Carroll <mattca@meta.com>
Google uses this on many of our API doc pages and it's not a good snippet. Only put this on the homepage but leave the og:description and twitter:description.
* Adds landing page for reference section.) * Updated hyperlinks. * Fixes Legacy APIs link. * Removes canary image from heading.
Co-authored-by: Sophie Alpert <git@sophiebits.com> Co-authored-by: Luna Wei <luwe@fb.com>
Co-authored-by: Soichiro Miki <smiki-tky@umin.ac.jp> Co-authored-by: David McCabe <davemccabe@gmail.com> Co-authored-by: Luna Wei <luwe@fb.com>
* Edits for new "use client" content * Apply suggestions from code review Co-authored-by: Luna <lunaleaps@gmail.com> --------- Co-authored-by: Luna <lunaleaps@gmail.com>
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>
Member
|
Superseded by #491. |
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
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 943e3ce
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.