-
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(schematics): secondary entry point migration not working against v9 #17452
fix(schematics): secondary entry point migration not working against v9 #17452
Conversation
Currently the secondary entry point migration uses the type checker to figure out which Material module a symbol belongs to. This won't work in v9, because we removed the top-level `@angular/material`. These changes fall back to looking up the name of the symbol in a list of known symbols and their module names. Fixes angular#17433.
src/material/schematics/ng-update/upgrade-rules/package-imports-v8/material-symbols.json
Show resolved
Hide resolved
...aterial/schematics/ng-update/upgrade-rules/package-imports-v8/secondary-entry-points-rule.ts
Show resolved
Hide resolved
...aterial/schematics/ng-update/upgrade-rules/package-imports-v8/secondary-entry-points-rule.ts
Show resolved
Hide resolved
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. Just one question (and replies to your questions)
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
src/material/schematics/ng-update/upgrade-rules/package-imports-v8/material-symbols.json
Show resolved
Hide resolved
...aterial/schematics/ng-update/upgrade-rules/package-imports-v8/secondary-entry-points-rule.ts
Show resolved
Hide resolved
...aterial/schematics/ng-update/upgrade-rules/package-imports-v8/secondary-entry-points-rule.ts
Show resolved
Hide resolved
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 the secondary entry point migration uses the type checker to figure out which Material module a symbol belongs to. This won't work in v9, because we removed the top-level
@angular/material
. These changes fall back to looking up the name of the symbol in a list of known symbols and their module names.Fixes #17433.