Skip to content

docs(dialog): remove unnecessary brackets #9207

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 2 commits into from
Jan 5, 2018
Merged

docs(dialog): remove unnecessary brackets #9207

merged 2 commits into from
Jan 5, 2018

Conversation

EdricChan03
Copy link
Contributor

@EdricChan03 EdricChan03 commented Jan 3, 2018

  • Removes the unnecessary brackets in the code snippet under the configuring dialog content... section.
  • Also rephrases the comment in the code snippet under the dialog content section.

- Removes the not needed brackets in the code snippet under the `configuring dialog content...` section.
- Also rephrases the comment in the code snippet under the `dialog content` section.
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jan 3, 2018
Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

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

LGTM

@crisbeto crisbeto added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Jan 3, 2018
@@ -81,7 +81,7 @@ For example:
<mat-dialog-content>Are you sure?</mat-dialog-content>
<mat-dialog-actions>
<button mat-button mat-dialog-close>No</button>
<!-- Can optionally provide a result for the closing dialog. -->
<!-- Optionally, a result can be provided for the closing dialog. -->
Copy link
Member

Choose a reason for hiding this comment

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

The grammar here isn't quite right. This should be:

The mat-dialog-close directive optionally accepts a value as a result for the dialog.

@jelbourn jelbourn removed the action: merge The PR is ready for merge by the caretaker label Jan 3, 2018
@EdricChan03
Copy link
Contributor Author

@jelbourn Comments have been addressed. Please take a look.

Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

@jelbourn jelbourn added the action: merge The PR is ready for merge by the caretaker label Jan 5, 2018
@jelbourn jelbourn merged commit 1cb4c31 into angular:master Jan 5, 2018
@EdricChan03 EdricChan03 deleted the patch-1 branch January 6, 2018 04:59
jelbourn pushed a commit to jelbourn/components that referenced this pull request Jan 8, 2018
jelbourn pushed a commit to jelbourn/components that referenced this pull request Jan 9, 2018
@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 Sep 8, 2019
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants