You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[x] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:
Current behavior
Currently mergeValidators/setValidators doesn't accept observables... we have the validateOn that deals with custom errors, but not with validators.
Expected behavior
I'd expect to see mergeValidators/setValidators accepting observables also, as setValue/patchValue.
What is the motivation / use case for changing the behavior?
I have an use case where I set the validators based on another formControl value, e.g.:
Also, I think we could add support to accept observable in mergeErrors/setErrors, that would remove the necessity of having validateOn... but that's just an idea.
Environment
Angular version: 10.x.y
The text was updated successfully, but these errors were encountered:
I'm submitting a...
Current behavior
Currently
mergeValidators
/setValidators
doesn't accept observables... we have thevalidateOn
that deals with custom errors, but not with validators.Expected behavior
I'd expect to see
mergeValidators
/setValidators
accepting observables also, assetValue
/patchValue
.What is the motivation / use case for changing the behavior?
I have an use case where I set the validators based on another
formControl
value, e.g.:Also, I think we could add support to accept observable in
mergeErrors
/setErrors
, that would remove the necessity of havingvalidateOn
... but that's just an idea.Environment
The text was updated successfully, but these errors were encountered: