Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Color. Inconsistency with the official tool
See original GitHub issueThank you for the awesome library. Let me describe the issue:
-
the color tool generates different result than the official tool that you also mention in the docs.
-
I have searched the issues of this repository and believe that this is not a duplicate.
Summary 💡
When user passes an override with only main color, the material-ui should set the light and dark not based on its own color tool, but using the official tool.
Motivation 🔦
Currently, having two I’d say main color tools (material-ui’s and the official one) producing different results lead to a misunderstanding.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I think the question is perhaps better phrased as “should the ‘official’ tool follow the guidelines.” to which I’d say yes.
@o-alexandrov Not sure if you missed the comment that the color tool output doesn’t match the spec palette tool output. That would need to be resolved first. Also, an API is definitely not the way to go, as this has runtime implications (not just docs), hence “breaking change”.