docs: add component class mixing guidelines#5737
Open
santiagopalma12 wants to merge 1 commit intocanonical:mainfrom
Open
docs: add component class mixing guidelines#5737santiagopalma12 wants to merge 1 commit intocanonical:mainfrom
santiagopalma12 wants to merge 1 commit intocanonical:mainfrom
Conversation
Closes canonical#5413 Added documentation explaining that component class names should not be mixed on the same element. Includes recommended usage examples and rationale for this convention.
|
santiagopalma12 is not a collaborator of the repo |
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
2 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.
Closes #5413
This PR adds documentation explaining that component class names should not be mixed on the same element.
Changes
Context
As noted in #5413, Vanilla has an unspoken style rule that component class names should not be mixed. This PR formalizes that convention in the documentation to help users avoid unexpected styling issues.