Repository navigation
docs: add <form> to React DOM components overview - #8717
Open
YashCoder-svg wants to merge 1 commit into
Open
YashCoder-svg wants to merge 1 commit into
YashCoder-svg wants to merge 1 commit into
Conversation
Size changesDetails📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
This branch was successfully deployed
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
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.
Description
This PR adds
<form>to the React DOM components overview page (src/content/reference/react-dom/components/index.md).<form>under the## Form componentssection alongside<input>,<select>, and<textarea>.<form>link in the## All HTML componentslist to point to the local React DOM<form>reference page (/reference/react-dom/components/form) rather than the external MDN link, matching the convention of all other built-in elements with dedicated React reference pages (<input>,<img>,<select>,<link>, etc.).Motivation
CONTRIBUTING.mdspecifies that the API Reference is intended to be exhaustive. While<form>received first-class support for Actions and a dedicated reference page in React 19, it was omitted from the Form Components section on the overview index page.How has this been tested?
Verified markdown formatting, heading IDs, and relative internal links locally.