Skip to content

refactor(ng-update): add links to migration guide in v9 hammer migration #17769

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

@devversion devversion commented Nov 21, 2019

  • Adds links to the migration guide in the v9 hammer migration
  • Cleans up the gesture config to be less verbose, and to work with the default TSLint configuration in CLI projects

* Adds link to the migration guide in the v9 hammer migration
* Cleans up the gesture config to be less verbose, and to work with the default TSLint configuration in CLI projects
@devversion devversion requested a review from jelbourn as a code owner November 21, 2019 11:07
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Nov 21, 2019
@@ -178,7 +178,8 @@ export class HammerGesturesRule extends MigrationRule<null> {
'The HammerJS v9 migration for Angular Components detected that HammerJS is ' +
'manually set up in combination with references to the Angular Material gesture ' +
'config. This target cannot be migrated completely, but all references to the ' +
'deprecated Angular Material gesture have been removed.');
'deprecated Angular Material gesture have been removed. Read more here: ' +
'https://git.io/ng-material-v9-hammer-ambiguous-usage');
Copy link
Member Author

Choose a reason for hiding this comment

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

I used git.io (which is an official Github service) since I don't want to show +150 chars for a perma-link. Happy to switch to something else if we can generate something like g.co/ng, or just use a real perma-link.

@@ -228,7 +230,8 @@ export class HammerGesturesRule extends MigrationRule<null> {
this.printInfo(
'The HammerJS v9 migration for Angular Components migrated the ' +
'project to keep HammerJS installed, but detected ambiguous usage of HammerJS. Please ' +
'manually check if you can remove HammerJS from your application.');
'manually check if you can remove HammerJS from your application. More details: ' +
'https://git.io/ng-material-v9-hammer-ambiguous-usage');
Copy link
Member Author

Choose a reason for hiding this comment

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

This overall message still feels somewhat exaggerated. It's not always ambiguous, and only rarely (see case 1 in the guide). @jelbourn do you have any idea how we can rephrase this and make it not sound like it's always wrong?

Copy link
Member

Choose a reason for hiding this comment

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

I think it's fine

@devversion devversion added pr: merge safe target: patch This PR is targeted for the next patch release labels Nov 21, 2019
@devversion devversion added this to the 9.0.0 milestone Nov 21, 2019
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

@@ -228,7 +230,8 @@ export class HammerGesturesRule extends MigrationRule<null> {
this.printInfo(
'The HammerJS v9 migration for Angular Components migrated the ' +
'project to keep HammerJS installed, but detected ambiguous usage of HammerJS. Please ' +
'manually check if you can remove HammerJS from your application.');
'manually check if you can remove HammerJS from your application. More details: ' +
'https://git.io/ng-material-v9-hammer-ambiguous-usage');
Copy link
Member

Choose a reason for hiding this comment

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

I think it's fine

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Nov 21, 2019
@jelbourn jelbourn merged commit bd3e2fb into angular:master Nov 21, 2019
@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 Dec 22, 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.

4 participants