I found a very helpful explanation about how to apply material theme color schemes/palettes for other non-material-components here.
Before I read this, I thought of something similar but couldn't imagine how to consider the recommendation from Theming your Angular Material app, if I don't want to have only global themes:
Your custom theme file should not be imported into other SCSS files. This will duplicate styles in your CSS output. If you want to consume your theme definition object (e.g., $candy-app-theme) in other SCSS files, then the definition of the theme object should be broken into its own file, separate from the inclusion of the mat-core and angular-material-theme mixins.
I wonder if this recommendation means that only global style sheets/ themes should be used? Otherwise I cannot imagine how to import the scss-theme into a component's scss-file without violating the above recommendation.
I am new to Sass and maybe missing something here.
You can find the pre-built theme files in the "prebuilt-themes" directory of Angular Material's npm package ( @angular/material/prebuilt-themes ). To include the pre-built theme in your application, add your chosen CSS file to the styles array of your project's angular.json file.
To do so, open the Settings and navigate to Appearance & Behavior → Material Theme UI → Custom Theme. Once you're done customizing your colors, you'll need to select Custom Theme or Light Custom Theme from the Theme Switcher to see your colors in action. Enjoy!
A theme is a set of colors that will be applied to the Angular Material components. To be more specific, a theme is a composition of color palettes.
Using a pre-built theme There are four pre-built material themes and they are: deeppurple-amber, indigo-pink, pink-bluegrey, and purple-green. If you're using Angular CLI, importing a theme into your application is as simple as including one line in your angular. json file.
I came across the same problem, some of the discussion can be found here, and an insighful blog dealing with the issue here.
Point is that - as the theming guide correctly states - you should never import mixins @include mat-core()
and @include angular-material-theme($your-theme)
more than once in your entire project. But when you're working with SASS in your components, you often do want to refer to your theme variables and mat-color palette. It's tempting to import your entire theme into the component SASS, accidentally duplicating the material mixins.
The solution I ended up with I think is the one the theming guide describes
the definition of the theme object should be broken into its own file, separate from the inclusion of the mat-core and angular-material-theme mixins
but since it was initially unclear to me how to do it, here's a step by step for anyone stuck with the same:
assets/styles/partials
folder containing SASS partialsMy folder looks like this:
assets/styles/partials/
_palette.scss // custom material palettes
_scaffolding.scss // general mixins
_theme.scss // <-- our theme definition
_variables.scss // global variables like fonts and colors
The _theme
partial contains the following:
// assets/styles/partials/_theme.scss
@import '~@angular/material/theming';
@import 'variables';
@import 'scaffolding';
@import 'palette';
$my-primary: mat-palette($mat-primary);
$my-accent: mat-palette($mat-accent);
$my-warn: mat-palette($mat-warn);
$my-theme: mat-light-theme($my-primary, $my-accent);
That's it. Do not include the material mixins mat-core
and angular-material-theme
in this file.
assets/styles/my-theme.scss
. It contains just three lines: // assets/styles/my-theme.scss
@import 'partials/theme'; // our actual theme definition
@include mat-core(); // the required mat-core mixin
@include angular-material-theme($my-theme); // the declaration of our custom material theme
By doing this we have separated our theme partial, including all our custome palette, scaffolding and variables, from the file that includes mat-core and our custom material theme.
"styles": [ "src/assets/styles/my-theme.scss" ]
With this, our app uses our custom material theme throughout, but because the theme definition (in the theme
partial) is separate from the inclusion of material mixins (in my-theme
), we can safely include our theme
partial into any component without duplicating any css.
Optionally, you can simplify the import of our theme partial by adding the partials path to the stylePreprocessorOptions in Angular.json:
"build": {
(...)
"options": {
(...)
"stylePreprocessorOptions": {
"includePaths": [
"src/assets/styles/partials"
]
}
}
}
Simply @import 'theme'
in any component scss file and we have access to all our variables and the material theming functions such as mat-color :)
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With