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

Use M3 in schematics and internal apps #28784

Merged
merged 4 commits into from Mar 27, 2024
Merged

Conversation

crisbeto
Copy link
Member

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.

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`.
@crisbeto crisbeto added target: major This PR is targeted for the next major release merge: preserve commits When the PR is merged, a rebase and merge should be performed labels Mar 27, 2024
@angular-robot angular-robot bot added detected: feature PR contains a feature commit area: docs Related to the documentation area: build & ci Related the build and CI infrastructure of the project labels Mar 27, 2024
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.
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Mar 27, 2024
@crisbeto crisbeto self-assigned this Mar 27, 2024
@@ -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;
Copy link
Contributor

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?

Copy link
Member Author

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.

@crisbeto crisbeto merged commit 00fe374 into angular:main Mar 27, 2024
26 of 27 checks passed
@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 Apr 27, 2024
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 area: build & ci Related the build and CI infrastructure of the project area: docs Related to the documentation detected: feature PR contains a feature commit merge: preserve commits When the PR is merged, a rebase and merge should be performed target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants