docs: mention forms support in outstanding controls - #33823
Merged
Merged
Conversation
crisbeto
approved these changes
Sep 18, 2026
crisbeto
added
action: merge
Member
crisbeto
pushed a commit
that referenced
this pull request
Sep 18, 2026
(cherry picked from commit bd54848)
crisbeto
pushed a commit
that referenced
this pull request
Sep 18, 2026
(cherry picked from commit bd54848)
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Having a
### Use with Angular Formssection was standardized for other controls, but now also includes:This change also makes sure to highlight
FormField(signal forms). No special mention to the API is included in this PR, as I just wanted to include this uniformity for now.For Select, this section is a H4, to highlight that 2-way binding is an alternative.