refactor(components): use semantic design tokens #950
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.
First attempt to use semantic tokens on components (here: accordion, badge, breadcrumb, button, card and link).
TBD:
Define what we actually expose as component dedicated CSS var as theme ones can be override specifically (see button example)
=> at least expose all computable values as a SCSS variable and a CSS var (referencing the SCSS var), this way it is easy to override locally a computed value, ex:
Accordion:
Badge:
Button:
Card:
Code:
Combobox:
Datepicker:
Divider:
Drawer:
(-still need to do overlay z-indexes)
FileUpload:
--ods-theme-text-color-success-ghost
to define default success text colorInput:
Message:
Meter:
Modal:
(-still need to do overlay z-indexes)
Pagination:
ProgressBar:
Range:
Select:
(-still need to do overlay z-indexes)
Skeleton:
Spinner:
Switch:
Table:
Tabs:
Tags:
Text:
Toggle:
Treeview: