Skip to content

docs(sidenav) property binding #9330

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 25, 2018

Conversation

ni-kit
Copy link
Contributor

@ni-kit ni-kit commented Jan 11, 2018

Should be a property binding according to docs.

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jan 11, 2018
@@ -1,5 +1,5 @@
<mat-sidenav-container class="example-container" *ngIf="shouldRun">
<mat-sidenav mode="side" opened="true">Sidenav content</mat-sidenav>
<mat-sidenav mode="side" [opened]="true">Sidenav content</mat-sidenav>
Copy link
Member

Choose a reason for hiding this comment

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

This can actually just be opened with no assignment

<mat-sidenav mode="side" opened>

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, you're right!
But maybe it should be more verbose for the sake of clarity? Brief search showed that it is common for the docs to have [bSome]="true" rather than just bSome.

Copy link
Member

Choose a reason for hiding this comment

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

In general I prefer to use the short form, otherwise people will interpret the examples as needing to be written out the long way.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Can I interpret that as a suggestion to fix every example in the docs according to your preferences?

Copy link
Member

Choose a reason for hiding this comment

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

If you want to correct other examples feel free to send additional PRs.

@jelbourn
Copy link
Member

@debudda do you want to make the change above to merge this PR?

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 pr: lgtm action: merge The PR is ready for merge by the caretaker labels Jan 25, 2018
@jelbourn jelbourn merged commit 6be3c64 into angular:master Jan 25, 2018
@jelbourn jelbourn added the target: patch This PR is targeted for the next patch release label Jan 29, 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 target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants