fix(parseToRGB): Not covered invalid input #323
Merged
Conversation
This file contains 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
Codecov Report
@@ Coverage Diff @@
## master #323 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 70 70
Lines 388 392 +4
Branches 102 104 +2
=====================================
+ Hits 388 392 +4
Continue to review full report at Codecov.
|
|
Thanks @tobilen I will take a look and try to get a release cut tonight. |
bhough
changed the title
bhough
approved these changes
Jun 28, 2018
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.
After upgrading to flow 0.75, i discovered that there is a case of invalid input that gets through the regex of the hsl matcher but not the one extracting color values from rgb. This PR should prevent this possibility.