Conversation
Codecov Report
@@ Coverage Diff @@
## master #436 +/- ##
==========================================
+ Coverage 91.84% 91.85% +<.01%
==========================================
Files 41 41
Lines 1337 1338 +1
Branches 193 168 -25
==========================================
+ Hits 1228 1229 +1
Misses 105 105
Partials 4 4
Continue to review full report at Codecov.
|
color propcolor prop
|
I like the implementing, and vote against using the primary as secondary as a color, as those are abstraction for something more then a color, that's why we have them as a properties. |
miroslavstastny
left a comment
There was a problem hiding this comment.
I think color palette (list of color names) should not be part of the API, but should be defined by a theme. Different themes should be able to define different list of colors.
If that's the case, colors cannot be enumerated in PropTypes, examples should read the list from current theme (see TextSizesExampleShorthand as an example).
Other opinions? @levithomason
We can define only base colors (i.e. black, white, blue, gray, etc) and leave |
|
Blocked by #423. |
|
Will be done as part of #451 to confirm that palette ideas are working. |
Fixes #423.
Refs #421, #426.
This PR adds the
colorprop for theDividercomponent.Blocked By
TODO
getColor()with testsAPI Proposal
ColorPaletteI took the SUI palette as reference:
I have doubts about
primaryandsecondarycolors, the code below looks very confusing:ComponentColorsA type that we will be used in props, defines all possible names of colors and includes
string.colorThe
colorprop accepts colors from the palette and custom colors.However, I'm also not sure about custom colors. It plays well semantically, however we have variables for this: