Fixes for Time Type Formats #226
Open
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
…(as opposed to DD) previously would have the | outside of parens and match crazy stuff
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Time formats were incorrectly matching due to some issues with the rexeps. Example:
{input: "2011", format: "D/M/YYYY"} would match incorrectly because the regex would be:
\d{1}|\d{2}/\d{1}|\d{2}/\d{4}
That finds the first \d{1} and calls it a day, rather than looking over the whole regex. Wrapping each element in parentheses fixes the issue.
I also added an explicit 'json' requirement to the Gemfile since it wasn't working with my newer version of rack. It's in its own commit.