refactor(forms): relax [formField] input type from FieldTree to Field#66951
Merged
mattrbeck merged 3 commits intoangular:mainfrom Feb 11, 2026
Merged
refactor(forms): relax [formField] input type from FieldTree to Field#66951mattrbeck merged 3 commits intoangular:mainfrom
mattrbeck merged 3 commits intoangular:mainfrom
Conversation
…Field` `FieldTree` was an unnecessarily specific type for the `[formField]` input. It forced the directive to care about what _kind_ of `FieldTree` was bound–specifically whether it was Reactive Forms compatible or not. This made it difficult to author forms system-agnostic components with passthrough `[formField]` inputs. This change introduces `Field`, which represents the callable state of a `FieldTree<TModel>` (e.g. `() => FieldState<TValue>`), without any of its the structure or compatibility concerns. Use of `FieldTree` for inputs is still appropriate when the component cares about the field's structure. For example: ```ts @component({ template: ` <street-address [formField]="address.street" /> <zip-code [formField]="address.zip" /> `, }) class Address { readonly address = input.required<FieldTree<Address>>(); } ```
mmalerba
suggested changes
Feb 9, 2026
mmalerba
approved these changes
Feb 9, 2026
Contributor
mmalerba
left a comment
There was a problem hiding this comment.
reviewed-for: public-api
Contributor
Author
|
Passing TGP. |
Contributor
Author
|
Note for caretaker: requires patch cl/867757980 |
mmalerba
approved these changes
Feb 11, 2026
Member
|
This PR was merged into the repository. The changes were merged into the following branches:
|
|
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
FieldTreewas an unnecessarily specific type for the[formField]input. It forced the directive to care about what kind ofFieldTreewas bound–specifically whether it was Reactive Forms compatible or not. This made it difficult to author forms system-agnostic components with passthrough[formField]inputs.This change introduces
Field, which represents the callable state of aFieldTree<TModel>(e.g.() => FieldState<TValue>), without any of its the structure or compatibility concerns.Use of
FieldTreefor inputs is still appropriate when the component cares about the field's structure. For example: