Skip to content

docs(form-field): use value getter when returning form data #18609

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

Merged
merged 1 commit into from
Feb 26, 2020
Merged

docs(form-field): use value getter when returning form data #18609

merged 1 commit into from
Feb 26, 2020

Conversation

tobiasschweizer
Copy link
Contributor

This PR fixes an inconsistency in the example for creating a custom form field control.

Now when writing to and updating the value from the custom form field control, the value's setter and getter are used. Instead of a mere object, the component interacting with the custom form field control now deals with an instance of MyTel.

resolves #18537

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Feb 25, 2020
Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks reasonable to me. @mmalerba should have a look.

@devversion devversion added the merge: fix commit message When the PR is merged, rewrites/fixups of the commit messages are needed label Feb 25, 2020
@jelbourn jelbourn changed the title feature (material examples): use value getter when returning form data docs(form-field): use value getter when returning form data Feb 25, 2020
Copy link
Contributor

@mmalerba mmalerba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mmalerba mmalerba added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Feb 25, 2020
@tobiasschweizer
Copy link
Contributor Author

@mmalerba @devversion Thanks for looking at this. I am not sure what's still needed for this PR to merged.

@devversion
Copy link
Member

@tobiasschweizer Thanks for the PR. No action is needed from your side. The PR will be merged soon.

@devversion devversion added the target: patch This PR is targeted for the next patch release label Feb 26, 2020
@jelbourn jelbourn merged commit 33f977c into angular:master Feb 26, 2020
@tobiasschweizer tobiasschweizer deleted the tobiasschweizer-issue-18537 branch February 26, 2020 15:18
jelbourn pushed a commit that referenced this pull request Mar 3, 2020
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Mar 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement merge: fix commit message When the PR is merged, rewrites/fixups of the commit messages are needed target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Guide: Creating a custom form field control
5 participants