This repository was archived by the owner on May 29, 2019. It is now read-only.
fix(datepicker): MinMaxInputValidation #3606
Closed
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
This was referenced May 8, 2015
There was a problem hiding this comment.
These new bindings should be optional
|
Going to close this in favor of #4841 - the approach there seems more elegant. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 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.
This PR is designed to fix #1688 and replaces my earlier PR #3020.
Enable min and max validation on datepicker popup input. Revised to only use one formatter and one parser per reviewer suggestions. Also, modified demo app to avoid scoping issues when binding to primitives. (See https://github.com/angular/angular.js/wiki/Understanding-Scopes)