-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
fix(ng-update): do not throw if imports without named bindings are used #12866
Conversation
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
return; | ||
} | ||
|
||
const namedBindings = node.importClause.namedBindings; |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…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
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
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