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
Use M3 in schematics and internal apps #28784
Conversation
Removes a guide that should've been deleted when we moved the MDC components to stable.
Updates the schematics to refer to the M3 prebuilt themes and to generate an M3 theme when the user selects `custom` in `ng add`.
Switches unit tests, the e2e app and SSR app to use the M3 themes by default.
Updates the dev app to use the same default theme as the docs and `ng add` schematic.
@@ -12,38 +12,38 @@ export function createCustomTheme(name: string = 'app') { | |||
// Custom Theming for Angular Material | |||
// For more information: https://material.angular.io/guide/theming | |||
@use '@angular/material' as mat; | |||
@use '@angular/material-experimental' as matx; |
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.
We probably don't want to include experimental stuff. Should we just wait on this until its moved out of experimental?
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.
I wanted to finish these instead of waiting for the code to be moved out of experimental. Once we do move them, it'll be quick to change the schematic.
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. |
See the individual commits for more info, but the tl;dr is that these changes switch us to using M3 themes in all our tests and internal apps.