-
Notifications
You must be signed in to change notification settings - Fork 26.2k
feat(forms): expose updateTreeValidity method #19829
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
3a3e33f to
5c404d6
Compare
5c404d6 to
a1ba27c
Compare
|
Hello? Don't want to hassle you. Sure you're busy. But this PR has some merge conflicts that you probably ought to resolve. |
1 similar comment
|
Hello? Don't want to hassle you. Sure you're busy. But this PR has some merge conflicts that you probably ought to resolve. |
|
ping :) would be awesome to have this functionality... working at the moment on a huge form and its really cumbersome to always have to manually iterate over nested forms to update validity or mark a larger part is dirty etc. |
|
+1. Need this as well. |
|
+1 Would love to remove the 'forEach' / recursvie functions we now have to fix this. |
|
I searched in the contributing guidelines but haven't found anything about opening a PR for a feature that already has a PR associated with. Since the last update on this one is from 2017, I was thinking about opening a new PR. |
|
What's the status with this? Did someone open a new PR? |
|
This will be a nice to have functionality, which reduce tons of repeated code in app. Can you please release this functionality as soon as possible ? |
|
+1 |
|
We're going to close this PR since it's out of date, but the issues both remain open and are still being discussed. |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: Closes #6170, closes #19820.
What is the new behavior?
Expose
AbstractControl#updateValueAndValidity()to allow user force re-validate aFormGroup.Does this PR introduce a breaking change?
Other information