Clean up theme colors & component hex values #164
Merged
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.
Untracked cleanup
What This Does
red
,yellow
, andgreen
colors to palettesuccess
,warning
anderror
to match the figma but it's pretty common for themes to both have named colors and aliased colors so that, for instance, you could have a theme that uses a different palette color for a state, e.g. a purple warning or a blue success. I think we should do this with all of the colors likeblue
andgray
at some point with aliases likeprimary
andbrand
. We already somewhat do this withtext
andborder
.theme.colors.*
instead of hard-coded hex valuesPill
component to better match designs overallcolor
prop totype
so that it matchessuccess | warning | error
nomenclatureguardian-ui
's<SideBar />
gateway-ui
's<Input />
Screenshots