Skip to content
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

fix(ng-update): do not throw if imports without named bindings are used #12866

Merged

Conversation

devversion
Copy link
Member

Currently if someone uses a namespace import or an import without named bindings in an Angular application, the ng-update schematics from Angular Material will fail due to missing safety checks before casting.

Fixes #11571

Currently if someone uses a namespace import or an import without named bindings in an Angular application, the `ng-update` schematics from Angular Material will fail due to missing safety checks before casting.

Fixes angular#11571
@devversion devversion added pr: merge safe target: major This PR is targeted for the next major release labels Aug 28, 2018
@devversion devversion requested a review from amcdnl as a code owner August 28, 2018 09:43
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Aug 28, 2018
return;
}

const namedBindings = node.importClause.namedBindings;
Copy link
Member Author

@devversion devversion Aug 28, 2018

Choose a reason for hiding this comment

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

Note: Storing the namedBindings here because future "import misc" cases will also always depend on the named bindings.

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 Aug 28, 2018
@jelbourn jelbourn merged commit cef2e1e into angular:master Aug 28, 2018
devversion added a commit to devversion/material2 that referenced this pull request Sep 5, 2018
…ed (angular#12866)

Currently if someone uses a namespace import or an import without named bindings in an Angular application, the `ng-update` schematics from Angular Material will fail due to missing safety checks before casting.

Fixes angular#11571
jelbourn pushed a commit that referenced this pull request Sep 5, 2018
…ed (#12866) (#12984)

Currently if someone uses a namespace import or an import without named bindings in an Angular application, the `ng-update` schematics from Angular Material will fail due to missing safety checks before casting.

Fixes #11571
@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.

Migration errors multiple TypeError
3 participants