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

Clarify precedence is arbitrary valued #6908

Merged
merged 1 commit into from
May 23, 2024
Merged

Conversation

gnoff
Copy link
Collaborator

@gnoff gnoff commented May 23, 2024

The docs for stylesheet precedence incorrectly state that there is an enumerated set of valid precedences. This is incorrect. The precedence value can be anything and React infers the hierarchy from the order in which it discovers precedences

The docs for stylesheet precedence incorrectly state that there is an enumerated set of valid precedences. This is incorrect. The precedence value can be anything and React infers the hierarchy from the order in which it discovers precedences
Copy link

vercel bot commented May 23, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
19-react-dev ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 24, 2024 10:25pm
react-dev ❌ Failed (Inspect) May 24, 2024 10:25pm

Copy link

Size changes

📦 Next.js Bundle Analysis for react-dev

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

@gnoff gnoff merged commit a25bd4b into reactjs:main May 23, 2024
5 of 6 checks passed
@gnoff gnoff deleted the clarify-precedence branch May 23, 2024 22:48
@souporserious
Copy link
Contributor

Thank you for the clarification in the docs! This makes much more sense now 😄

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

Successfully merging this pull request may close these issues.

4 participants