This repository has been archived by the owner on Nov 22, 2021. It is now read-only.
Option not to validate an "untouched" control #784
Comments
alivraghi
pushed a commit
to alivraghi/ngTagsInput
that referenced
this issue
Mar 23, 2017
Add an option for the user to set avoid validation on untouched control. Closes mbenford#784.
alivraghi
pushed a commit
to alivraghi/ngTagsInput
that referenced
this issue
Apr 12, 2017
Add an option for the user to set avoid validation on untouched control. Closes mbenford#784.
alivraghi
pushed a commit
to alivraghi/ngTagsInput
that referenced
this issue
Apr 12, 2017
…into focus-merge er to set avoid validation on untouched control. Closes mbenford#784.
alivraghi
pushed a commit
to alivraghi/ngTagsInput
that referenced
this issue
Apr 19, 2017
Add an option for the user to set avoid validation on untouched control. Closes mbenford#784.
alivraghi
pushed a commit
to alivraghi/ngTagsInput
that referenced
this issue
Apr 19, 2017
Add an option for the user to set avoid validation on untouched control. Closes mbenford#784.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
thanks a lot for the good job!
This is a request rather than a defect.
It could be nice to have the option not to validate a control at init time, in other words, when the control is untouched.
So far, setting
min-tagsattribute greater than zero implies always invalidation. This behavior is quite annoying on a form with other controls because appears invalid only the tags field even if the user hasn't done anything yet.Alvaro
The text was updated successfully, but these errors were encountered: