-
Notifications
You must be signed in to change notification settings - Fork 26.3k
feat(forms): Add FormArrayDirective
#55880
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
base: main
Are you sure you want to change the base?
Conversation
35741f0
to
2d950c1
Compare
2d950c1
to
f29120d
Compare
f29120d
to
25997b4
Compare
25997b4
to
d6271bb
Compare
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.
@JeanMeche I had a quick look and the changes look good. I want to ask if you could split the commit into 2:
- first
refactor
commit performs a refactoring and extracts out the common logic into the abstract form directive class - the second
feat
commit that adds a new directive
That should help to make the change more incremental and help with more detailed code review.
7a959ab
to
e7d47d9
Compare
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.
Thanks for splitting up the change in this way! Let's merge this after the RC, so we can get it on the 18.2 track, and we'll have plenty of time to receive feedback from GDEs and other early users.
151fb16
to
db3aebe
Compare
157202d
to
74d6af2
Compare
G3 has been cleaned-up but bummer we missed the v20 breaking change window. This is a breaking change due to the typing change for the |
Converting back to draft until we enter the breaking change window. |
Ahead of the implementation of `FormArrayDirective`, extract the shared logic into an abstract class.
The `FormArrayDirective` will allow to have a `FormArray` as a top-level form object. * `NgControlStatusGroup` directive will be applied to the `FormArrayDirective` * `NgForm` will still create a `FormGroup` Fixes angular#30264 BREAKING CHANGE: This new directive will conflict with existing FormArray directives or formArray inputs on the same element.
74d6af2
to
bcb0bfc
Compare
The
FormArrayDirective
will allow to have aFormArray
as a top-level form object.NgControlStatusGroup
directive will be applied to theFormArrayDirective
NgForm
will still create aFormGroup
Usage :
Fixes #30264
BREAKING CHANGE: The
formDirective
getter onFormGroupName
andFormArrayName
now return aAbstractFormDirective