New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs(forms): add comment of the 'value' property #29898
Conversation
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
@Ly-lns the CLA requirement must be resolved before this PR can move forward. |
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
@brandonroberts thanks.The CLA is signed now! |
39aaa3c
to
d7c3a17
Compare
Caretaker note: This is a docs only change and should not impact g3. Please run presubmit. |
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. |
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: 15982
#15982
According to the above issue,we can know that for an enabled FormGroup,the 'value' property only contain the enabled values of its children.Howerve,for a disabled FormGroup,the 'value' property contain all the values of its children.This should be written in the comment.
What is the new behavior?
Does this PR introduce a breaking change?
Other information