[Themes] colorManipulator cleanup #3966
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.
This started out as work to fix a bug in
lighten()
that was affecting styling inChip
, but it soon became apparent that there were broader issues.This PR has three commits:
[Themes] Remove default export from colorManipulator
[Themes] Overhaul colorManipulator
lighten()
- it returned incorrect valueslighten()
- remove default alpha (usefade()
instead)darken()
- it returned incorrect values, and was foobar for hslconverColorToString()
- Correct hsl output (adds '%' where needed)decomposeColor()
- return values as numbers not stringsPreviously it broke formula where addition of a number to a string resulted in a string ('2' + 2 = '22')
getContrastRatio()
formula - remove conditionalgetContrastRatio()
(return a number, not a string)getContrastRatioLevel()
(dead code)getLuminance()
to support hslfade()
@param
tags[Themes] Move some duplicate logic out of getMuiTheme.js
emphasize()
which darkens a light color and lightens a dark color according to luminance. (Will be used inChip
)getMuiTheme.js
to use the new function.