-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Angular v15 Material API Changes Causes Production Build Design Issues #69
Comments
Update: I ended up spending the time to convert all the @matheo if you are still around and supporting this library, if I make a pull request to fix these issues for v15, will you be able to review and approve my PR? The issue is pretty minor, since I'm sure I could target the elements through global styles, but it would be much better to fix this for the community. |
Got a fork? |
Sorry, no. Ended up going with a different package: https://www.npmjs.com/package/@ng-matero/extensions (That other reply was my work account) |
Quick solution to fix the styles of this deprecated library. @mixin......
$hover: map-get($background, hover);
.mat-custom-prev-next {
align-items: center;
}
.mat-calendar-previous-button,
.mat-calendar-next-button {
cursor: pointer;
width: 42px;
height: 42px;
background-color: transparent;
border-color: transparent;
border-radius: 50%;
margin: 0 2px;
&:hover {
background-color: $hover;
}
&::after {
margin: 14px;
}
}
.mat-custom-time-hour,
.mat-custom-time-minute {
height: fit-content;
font-size: 56px;
line-height: 56px;
} |
Describe the bug
I wish I had more information on this, I'm still working through a suitable solution.
After upgrading from Angular 14 to 15, and still using the "Legacy" API for all Material related things, the only issue I've noticed is that any Material based component used by this library is not getting any style applied to it. It works and looks fine in development, but after building the production build and deploying, the styles are just not there/very ugly.
Minimal Reproduction
Start with an Angular 14 application, implement Angular Material + this library, then run the upgrades to angular 15. I believe the way the @include datepicker.theme($theme); is working is causing the library to use the "new" API rather than the legacy API.
It's possible I just need to bite the bullet and upgrade to the "new" Material MDC API. But it would be nice to have an option to provide a legacy theme builder to this library.
Expected behavior
I would expect the styles to look the same between dev and production.
Screenshots
Your Environment
The text was updated successfully, but these errors were encountered: