feat(forms): Add FormArrayDirective#55880
Conversation
35741f0 to
2d950c1
Compare
2d950c1 to
f29120d
Compare
f29120d to
25997b4
Compare
25997b4 to
d6271bb
Compare
AndrewKushnir
left a comment
There was a problem hiding this comment.
@JeanMeche I had a quick look and the changes look good. I want to ask if you could split the commit into 2:
- first
refactorcommit performs a refactoring and extracts out the common logic into the abstract form directive class - the second
featcommit 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
dylhunn
left a comment
There was a problem hiding this comment.
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. |
74d6af2 to
bcb0bfc
Compare
Ahead of the implementation of `FormArrayDirective`, extract the shared logic into an abstract class.
bcb0bfc to
35d29fe
Compare
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.
thePunderWoman
left a comment
There was a problem hiding this comment.
LGTM!
reviewed-for: fw-general, public-api
mmalerba
left a comment
There was a problem hiding this comment.
reviewed-for: public-api
|
This PR was merged into the repository. The changes were merged into the following branches:
|
This comment was marked as off-topic.
This comment was marked as off-topic.
|
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. |
The
FormArrayDirectivewill allow to have aFormArrayas a top-level form object.NgControlStatusGroupdirective will be applied to theFormArrayDirectiveNgFormwill still create aFormGroupUsage :
Fixes #30264
BREAKING CHANGE: The
formDirectivegetter onFormGroupNameandFormArrayNamenow return aAbstractFormDirective