Skip to content

refactor(schematics): rename migration entry-points #13333

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

devversion
Copy link
Member

  • In favor of consistency, we should rename the migration entry-points for Material similarly to the CDK migration entry-points. Also migration-01 and migration-01 is pretty much saying nothing about what it does.

* In favor of consistency, we should rename the migration entry-points for Material similarly to the CDK migration entry-points. Also `migration-01` and `migration-01` is pretty much saying nothing about what it does.
@devversion devversion added pr: merge safe target: major This PR is targeted for the next major release labels Sep 27, 2018
@devversion devversion requested a review from amcdnl as a code owner September 27, 2018 08:16
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Sep 27, 2018
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 Sep 27, 2018
@jelbourn jelbourn merged commit 3192dfa into angular:master Sep 27, 2018
roboshoes pushed a commit to roboshoes/material2 that referenced this pull request Oct 23, 2018
* In favor of consistency, we should rename the migration entry-points for Material similarly to the CDK migration entry-points. Also `migration-01` and `migration-01` is pretty much saying nothing about what it does.
@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 9, 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: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants