This repository has been archived by the owner on May 29, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
feat(dateParser): Add support for HH, H, mm, m, ss, s formats #3417
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should instead do this right before the
new RegExp()
call insidecreateParser
as that shows why this character replacement is needed (it's to be fed into the RegExp constructor).There's also less weird characters to process in the
createParser
'sformatCodeToRegex
loop.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explain the less weird characters part? Just moving this inside the
createParser
function isn't enough, there seems to be some specificity required as to when the parsing happens since the regex gets some additional characters through the iteration overformatCodeToRegex
. The loop adds an open and closed set of parentheses to the regex. This means that it would be too late to modify the format string at that stage.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm yea, I'm referring to replacing the characters right before the parentheses are added.
With the less weird characters, I'm referring to that if given a format of
hh:mm
, thecreateParser
will now receivehh\:mm
as the format when you do this here. It doesn't need that extra\
when looking forhh
ormm
(in theangular.forEach(formatCodeToRegex…
block), it only needs the extra\
right before creating theregex
property when feeding it into theRegExp
constructor with the parentheses.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As per discussion between @chrisirhc and I on Slack, this turns out to be the best spot for modifying the format given how the iteration in
formatCodeToRegex
is implemented.