add validateOn to ng-model-options to make the $parsers run even when updates are pending

[shahata]

On many cases it makes sense to have something like {updateOn: 'blur', validateOn: 'default'}. If this sounds reasonable to you I can have this PR ready this week. @petebacondarwin @lrlopez @IgorMinar - what do you think about this?

[petebacondarwin]

Waiting for new validator pipeline to be merged before tackling this one.

[shahata]

@petebacondarwin I've rebased this with the new validator pipeline change, but I think it needs to wait until #7836 is resolved

[pocesar]

+1

[IgorMinar]

I'm not a fan of this because it only adds more options and states without clear benefits.

[IgorMinar]

Can you provide some strong use-cases that are not possible to implement in Angular 1.3 today?

[shahata]

@IgorMinar I've discussed this with @petebacondarwin a couple of months ago and we both agreed that we don't see a very strong use case for this. I don't mind closing this and wait to see if someone asks for something similar in the future.

[levic]

A use case that would be handled easily with validateOn

http://plnkr.co/6vRyCd94k36B6EDXPcmr

By using ngModelOptions="{updateOn: 'submit'}" it allows you to not have to shadow the ng-model data you are modifying.

Unfortunately it also means that it is not possible to easily provide validation feedback to the user. Adding validateOn would make this much simpler.

[BoLaMN]

i had the same use case as @levic so i made two decorators to enable this functionality

https://github.com/BoLaMN/angular-validate-on

[sryzycki]

+1