Add strict mode to strictly match hex tokens #4
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
Closed
|
Cool. I'll amend my commit so the version number is 1.0.2 here in a bit. I'll leave the restyling of the README to you. 😄 |
|
@btholt sorry for the delay, i come to it... lol. I'll try to push it up today. |
This was referenced Jun 1, 2015
|
@btholt hm... is that should return false? hexColorRegex().test('#123fff}')
//=> true, now/cc @regexps/owners |
|
@btholt published as |
|
Hooray! Thank you! |
|
Yea, sorry for the long delay. 🍺 |
|
No apology necessary. I'm hugely appreciative. 🎉 |
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.
Went ahead and did it.