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
Which @angular/* package(s) are the source of the bug?
forms
Is this a regression?
Yes
Description
As you can see in the image, I have an input with a custom validator and I send a signal into it.
Inside the validator, I get that value and use it in my validate function.
The validate function is only called when the input value that has the validator changes, but doesn't when the "entregaName" value changes. I understand that maybe this is not the correct way of doing it, however it's what seems common sense.
My use case is I want to validate an input whenever the users click a button. I can't use async validators because they would fire each time.
In the past I've used the hack of adding a space to the input and then deleting the space with a settimeout, thus activating the validation function, aswell as adding or removing errors from the control programatically, but it doesn't seem like the proper way of doing it.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in (run ng version)
Which @angular/* package(s) are the source of the bug?
forms
Is this a regression?
Yes
Description
As you can see in the image, I have an input with a custom validator and I send a signal into it.
Inside the validator, I get that value and use it in my validate function.
The validate function is only called when the input value that has the validator changes, but doesn't when the "entregaName" value changes. I understand that maybe this is not the correct way of doing it, however it's what seems common sense.
My use case is I want to validate an input whenever the users click a button. I can't use async validators because they would fire each time.
In the past I've used the hack of adding a space to the input and then deleting the space with a settimeout, thus activating the validation function, aswell as adding or removing errors from the control programatically, but it doesn't seem like the proper way of doing it.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
No response
The text was updated successfully, but these errors were encountered: