Repository navigation
docs: correct web API descriptions and examples - #342
Open
dajiaohuang wants to merge 1 commit into
Open
dajiaohuang wants to merge 1 commit into
dajiaohuang wants to merge 1 commit into
Conversation
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
This branch has not been 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.
Summary
Correct existing web API documentation and copyable examples to match the current implementation:
gradientRatiodefaults to2, and SVG ids now come fromReact.useId(since fix(hydration): useuseIdfor dom variant #325); explain whenuniqueKeyis useful without requiring it for ordinary SSR.gradientDirectionstory: the current public type and SVG implementation do not support this prop, so both advertised directions render the same horizontal animation.<base href>attribute.No animation design, component behavior or public API changes.
Related Issue
No companion issue. The generated-id explanation follows the already merged #325.
Any Breaking Changes
None; documentation/examples only.
Checklist
vite@4); the initial legacy-peer install omitted Vite. No dependency/lockfile changes included.Not a Safari/Firefox, React Native device, or assistive-technology validation. Existing package-manager and ReactDOM.render deprecation warnings are unchanged.