Skip to content
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.

min/max validator fixes to number and date inputs #8913

Closed
wants to merge 5 commits into from

Conversation

matsko
Copy link
Contributor

@matsko matsko commented Sep 3, 2014

Closes #2404
Closes #6755

@caitp
Copy link
Contributor

caitp commented Sep 3, 2014

LGTM for numbers (but I believe min/max also has a meaning for various date inputs too)

@matsko
Copy link
Contributor Author

matsko commented Sep 3, 2014

Thx. I'm changing the commit message of the first commit to reflect that.

@btford btford added this to the 1.3.0-rc.1 milestone Sep 3, 2014
@matsko matsko force-pushed the pr_2404 branch 2 times, most recently from d6fa37f to 546ffaf Compare September 3, 2014 22:01
…nge for number inputs

As of this fix if the max or min value is changed via scope or by another ngModel
then it will trigger the model containing the min/max attributes to revalidate itself.

Closes angular#2404
…t types

With this fix ngModel will treat ngMin as a min error and ngMax as a max error.
This also means that when either of these two values is changed then ngModel will
revaliate itself.
Due to the nature of how date objects are rendered when JSON.stringify
is called, the resulting string contains two sets of quotes surrounding
it. This commit fixes that issue.

Closes angular#6755
@matsko matsko changed the title fix min/max issues with input[type="number"] min/max validator fixes to number and date inputs Sep 4, 2014
@matsko matsko closed this Sep 4, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
4 participants