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 introduces a
secondary
variant of theTag
component. I'm looking for feedback and feasibility in merging this in advance of the Admin UI Foundations projectWHY are these changes introduced?
We're run into an issue where we have a component that contains both badges and tags and we'd like those to visually match. There's currently no way to achieve this without CSS overrides. Since we expect a secondary treatment to be coming I'm using this PR to test the waters in introducing this treatment now.
WHAT is this pull request doing?
This adds a "secondary" variation of the Tag that is compatible with all other variants and lightens the background to use
bg-secondary
as shown:Note that on a secondary background the
Tag
background color will blend inCurrently includes:
How to 🎩
🖥 Local development instructions
🗒 General tophatting guidelines
📄 Changelog guidelines
🎩 checklist
README.md
with documentation changes