-
Notifications
You must be signed in to change notification settings - Fork 6.8k
feat: add mixins for density styles of all components #18761
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
Conversation
// discussion as it would introduce a circular dependency for typography because: | ||
// -> `all-theme` -> `mat-core` -> `all-typography` -> `all-theme`. | ||
// This happens because developers rely on the `mat-core` to be available when | ||
// the `all-theme` file is imported. |
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.
A possible solution would be that developers need to explicitly import the file that exposes the mat-core
mixin. We can also keep it as is for now and import the individual typography mixins.
126c082
to
cf28dc0
Compare
Similarly to `mdc-density`, we add a mixin for all of the density styles that will exist in `src/material`. Additionally, mdc-typography and mdc-theming mixins are simplified now that the `all-theme` mixins can control individual theming system parts. This does not work for `@angular/material` typography due to a cyclic dependency which we could eliminate if we require people to _explicitly_ import the file where the `mat-core` mixin originates from.
cf28dc0
to
cb2b3a3
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.
LGTM
Similarly to `mdc-density`, we add a mixin for all of the density styles that will exist in `src/material`. Additionally, mdc-typography and mdc-theming mixins are simplified now that the `all-theme` mixins can control individual theming system parts. This does not work for `@angular/material` typography due to a cyclic dependency which we could eliminate if we require people to _explicitly_ import the file where the `mat-core` mixin originates from.
Similarly to `mdc-density`, we add a mixin for all of the density styles that will exist in `src/material`. Additionally, mdc-typography and mdc-theming mixins are simplified now that the `all-theme` mixins can control individual theming system parts. This does not work for `@angular/material` typography due to a cyclic dependency which we could eliminate if we require people to _explicitly_ import the file where the `mat-core` mixin originates from.
Similarly to `mdc-density`, we add a mixin for all of the density styles that will exist in `src/material`. Additionally, mdc-typography and mdc-theming mixins are simplified now that the `all-theme` mixins can control individual theming system parts. This does not work for `@angular/material` typography due to a cyclic dependency which we could eliminate if we require people to _explicitly_ import the file where the `mat-core` mixin originates from.
Similarly to `mdc-density`, we add a mixin for all of the density styles that will exist in `src/material`. Additionally, mdc-typography and mdc-theming mixins are simplified now that the `all-theme` mixins can control individual theming system parts. This does not work for `@angular/material` typography due to a cyclic dependency which we could eliminate if we require people to _explicitly_ import the file where the `mat-core` mixin originates from.
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. |
Similarly to
mdc-density
, we add a mixin for all of the density stylesthat will exist in
src/material
.Additionally, mdc-typography and mdc-theming mixins are simplified
now that the
all-theme
mixins can control individual theming systemparts. This does not work for
@angular/material
typography due toa cyclic dependency which we could eliminate if we require people
to explicitly import the file where the
mat-core
mixin originates from.