Repository navigation
fix(color): allow whitespace around a color name, like the other formats - #442
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Color(" 777 ")andColor(" rgba(0, 0, 128, 0.6) ")are accepted (both are intest_color_success), but a named color with surrounding whitespace, such asColor("red ")orColor(" transparent"), was rejected with "string not recognised as a valid color", because the name lookup used the string as is.parse_str()now strips the value before the lookup, so names andtransparentaccept whitespace like every other format.original()still returns the input unchanged. Added cases totest_color_success.