Skip to content

refactor(ng-update): handle namespaced angular decorators in update-tool #17737

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 18, 2019

Previously Angular did not support namespaced Angular decorators. e.g.

@core.Component({...})
@core.Directive({...})

Since this is now supported in ngtsc, we want to handle
such cases where stylesheets, templates are referenced in
namespaced decorators.

This can be achieved by moving the more advanced import
resolution logic made for the Hammer gesture migration
to the cdk/update-tool. Exposing these for other CDK
and Material migrations can be helpful anyway.

This also unveiled that we did not run non-misc test cases
automatically. This will be fixed as part of this commit.

@devversion devversion added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent pr: merge safe target: patch This PR is targeted for the next patch release labels Nov 18, 2019
@devversion devversion requested a review from jelbourn as a code owner November 18, 2019 09:16
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Nov 18, 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

Previously Angular did not support namespaced Angular decorators. e.g.

```
@core.Component({...})
@core.Directive({...})
```

Since this is now supported in ngtsc, we want to handle
such cases where stylesheets, templates are referenced in
namespaced decorators.

This can be achieved by moving the more advanced import
resolution logic made for the Hammer gesture migration
to the `cdk/update-tool`. Exposing these for other CDK
and Material migrations can be helpful anyway.

This also unveiled that we did not run non-misc test cases
automatically. This will be fixed as part of this commit.
@devversion devversion force-pushed the refactor/ng-update-handle-namespaced-imports branch from c480255 to ba01d63 Compare November 18, 2019 17:21
@devversion devversion added the action: merge The PR is ready for merge by the caretaker label Nov 18, 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

@jelbourn jelbourn merged commit a5437cd into angular:master Nov 18, 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 19, 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 P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent 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