-
Notifications
You must be signed in to change notification settings - Fork 26.3k
feat(forms): add ability to clear a FormRecord #50750
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
ce2375e
to
54abda7
Compare
c5b31ad
to
537a617
Compare
Any update on this PR please ? |
What's blocking this? |
5ec23e9
to
656e5b0
Compare
Let me help to see where we can go with this change. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Preliminary tests against the Google codebase came back green.
Running a TGP (googler link). |
@EmmanuelRoux Would you mind rebasing this on |
656e5b0
to
3b077e6
Compare
@dylhunn done 👍 |
Add unit test for statusChange events PR Close #50750
This reverts commit b0c4c1f.
This reverts commit 3e7d724.
This reverts commit 18b6f33.
FYI, reopening this PR due to a breakage in Google's codebase (typing-related). Reverted via #58315, the change will need a global presubmit (TGP). Next step is for the Angular team to run TGP and investigate failures. |
The changelog mentions this new function (https://github.com/angular/angular/blob/main/CHANGELOG.md#forms-1) for v19.0.0 There's no mention in the changelog of it being reverted so this is a bit misleading, and it's unclear which versions (if any) shipped with it before being reverted. |
@Nallebeorn The feature was indeed un-shipped, we'll update the changelog. |
7c707ed
to
0fedf2c
Compare
The rebase didn't go as expected, can you cherry pick your 3 commits (visible here https://github.com/EmmanuelRoux/angular/commits/7c707ed6f5) so we can reopen the PR. |
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: fixes #50748 and #50751
What is the new behavior?
New method
FormRecord.clearControls()
is available.Does this PR introduce a breaking change?
Other information