fix(forms): Allow NonNullableFormBuilder to be injected.#45904
fix(forms): Allow NonNullableFormBuilder to be injected.#45904dylhunn wants to merge 1 commit intoangular:mainfrom
NonNullableFormBuilder to be injected.#45904Conversation
|
@AndrewKushnir I'm actually unsure of how to unit test this, do any suggestions come to mind? |
You can add a test like this: I'd propose adding a similar test for |
e8ccb79 to
6ba5fd4
Compare
AndrewKushnir
left a comment
There was a problem hiding this comment.
Looks good 👍 Just left a couple minor comments.
AndrewKushnir
left a comment
There was a problem hiding this comment.
Reviewed-for: public-api
jessicajaniuk
left a comment
There was a problem hiding this comment.
reviewed-for: public-api
|
Currently running a standard presubmit. |
|
merge-assistance: I'm not sure why pullapprove is fighting me, this is good to go |
|
@dylhunn could you please update the code based on #45904 (review)? |
Based on early feedback, calling `fb.nonNullable.group(...)` continues to be clunky for a form with many such groups. Allowing `NonNullableFormBuilder` to be directly injected enables the following:
```
constructor(private fb: NonNullableFormBuilder) {}
```
|
@AndrewKushnir Whoops, now fixed. |
|
This PR was merged into the repository by commit 43ba4ab. |
Based on early feedback, calling `fb.nonNullable.group(...)` continues to be clunky for a form with many such groups. Allowing `NonNullableFormBuilder` to be directly injected enables the following:
```
constructor(private fb: NonNullableFormBuilder) {}
```
PR Close #45904
|
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. |
Based on early feedback,
fb.nonNullable.group(...)continues to be clunky for a form with many such groups. AllowingNonNullableFormBuilderto be directly injected enables the following: