-
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
feat(material/schematics): add migration to switch to the new theming API #22304
Conversation
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.
Looks good to me (given the amount of context I have). Jeremy's comment for Copybara sounds reasonable to me.
I think that's okay for now- we'll see how rollout goes and whether we need to do anything special for now-really-private APIs. |
9c75771
to
d95e8d6
Compare
@jelbourn I've expanded the migration to handle any |
d95e8d6
to
ae1c4e9
Compare
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.
Looks good overall, just one main comment about identifying @use
namespaces
… API Adds an `ng-generate` schematic that will switch over existing stylesheets to the new `@use`-based API. Furthermore, the migration code is set up in a way that should allow us to run it in g3 if necessary.
ae1c4e9
to
517cf91
Compare
I've reworked it based on the latest set of feedback. |
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, masterful
This is follow-up from the PR that introduced the theming API migration (angular#22304 (comment)). It renames a few variables in the CDK to align them with the new API.
This is follow-up from the PR that introduced the theming API migration (#22304 (comment)). It renames a few variables in the CDK to align them with the new API.
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. |
Adds an
ng-generate
schematic that will switch over existing stylesheets to the new@use
-based API. Furthermore, the migration code is set up in a way that should allow us to run it in g3 if necessary.