feat(forms): allow permanent hidden fields in signal forms#69820
Open
brysonbw wants to merge 1 commit into
Open
feat(forms): allow permanent hidden fields in signal forms#69820brysonbw wants to merge 1 commit into
brysonbw wants to merge 1 commit into
Conversation
angular-robot
Bot
added
detected: feature
Member
|
Can you please check the CI failures. Thank you. |
Allow the hidden utility function to be called without a configuration object to make fields permanently hidden.
brysonbw
force-pushed
the
feat-allow-permanent-hidden-fields-to-signal-forms-68278
branch
from
July 16, 2026 13:19
5e93729 to
d0d1d88
Compare
JeanMeche
approved these changes
Jul 16, 2026
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number:
What is the new behavior?
Does this PR introduce a breaking change?
Other information
readonly()anddisabled()signal form rules