Skip to content

chore(snack-bar): rename MdSnackBarRef instance to componentInstance #6566

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

Conversation

shaunak1111
Copy link

@jelbourn Please review the PR

instance is renamed to componentInstance to be consistent with other dialogs

Closes angular#6252
instance is renamed to componentInstance to be consistent with other dialogs

Closes angular#6252
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Aug 20, 2017
@jelbourn jelbourn changed the title Snack bar ref component instance change chore(snack-bar): rename MdSnackBarRef instance to componentInstance Aug 21, 2017
@@ -15,8 +15,8 @@ import {MdSnackBarContainer} from './snack-bar-container';
* Reference to a snack bar dispatched from the snack bar service.
*/
export class MdSnackBarRef<T> {
/** The instance of the component making up the content of the snack bar. */
instance: T;
/** The instance of snack bar. */
Copy link
Member

Choose a reason for hiding this comment

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

The old comment was correct

instance is renamed to componentInstance to be consistent with other dialogs

Closes angular#6252
@jelbourn
Copy link
Member

@shaunak1111 can you squash this into one commit with a breaking change message?
(similar to #5419)

…ackBarRef_componentInstance_change

# Conflicts:
#	src/lib/snack-bar/snack-bar.spec.ts
@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 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
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.

3 participants