We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
With the specific following instructions, regenerate produces a non-minimal (but correct) regex:
regenerate().addRange( 99, 100 ).addRange( 65, 99 ).toString() '[cdA-c]'
By switching the order, we have a correct minimal regex:
regenerate().addRange( 65, 99 ).addRange( 99, 100 ).toString() '[A-d]'
Playing a bit with the boundaries, it seems it only occur when the end of the second range is exactly the same as the start of the first range.
The text was updated successfully, but these errors were encountered:
Good catch. Looks like we have an off-by-one somewhere. Patches welcome!
Sorry, something went wrong.
Fix an edge case creating non-minimal ranges
008df09
Closes mathiasbynens#37.
Fix an edge case creating non-minimal ranges (#38)
921b383
Closes #37.
Successfully merging a pull request may close this issue.
With the specific following instructions, regenerate produces a non-minimal (but correct) regex:
By switching the order, we have a correct minimal regex:
Playing a bit with the boundaries, it seems it only occur when the end of the second range is exactly the same as the start of the first range.
The text was updated successfully, but these errors were encountered: