check color names #350
Merged
check color names #350
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rotu
force-pushed
the
Typed-color-names
branch
from
bdeab92 to
acc545d
Compare
0b5vr
reviewed
Feb 13, 2023
|
|
||
| export { SRGBToLinear } from './ColorManagement'; | ||
|
|
||
| declare const _colorKeywords: { |
Contributor
There was a problem hiding this comment.
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Why
Color's constructor previously allowed invalid color names, which fail at runtime with a warning.What
Now colornames will be checked by typescript and will autocomplete in supporting ides.
E.g.
new Color('blu')will fail to typecheck.Checklist
master, next goesdev)