This repository has been archived by the owner on Nov 30, 2021. It is now read-only.
Allow amDateFormat to work with custom formatted input date strings #162
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
urish
added a commit
that referenced
this pull request
Aug 20, 2015
Allow amDateFormat to work with custom formatted input date strings
|
Looks good, thanks! |
|
Released as 0.10.3 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The amDateFormat filter only works with date strings that follow a known, standard date format. If I'm trying to use that filter on a differently formatted time string it just fails.
This adds an inputFormat parameter to the amDateFormat filter and allows the filter to use the angularMomentConfig.format variable to set a different format to expect date inputs to follow.