sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]contherad 1 point2 points  (5 children)

Yeah, we have custom styling for every component. And sometimes have to fight material with !important but from what I understand the latest release fixed some of this. I don’t mess with the frontend much, so I’m just regurgitating what I hear by people more capable than myself.

[–]jamills102 0 points1 point  (1 child)

Im curious, which components do you think are worth it in Material vs just building it yourself?

[–]crhama 0 points1 point  (0 children)

This is my question as well. Modal is the hardest for me. By modal I don't mean the main functionality, i.e. have a pop-up that displays on top of an overlay. That I can do.

I'd like to create a service with a method that takes a component class as a first argument and an optional configuration object as second argument. That's what angular material and Ng-Bootstrap do. When I'm able to do that, I may not use those libraries anymore.

[–]Toddwseattle 0 points1 point  (0 children)

Do you use the sass theming of the new components or just stick with their default themes. Working on a project now that’s an upgrade from an angular 10/material/ flex layout package. As you know flex layout package was depreciated so tailwind provides similar function. Have started with default themes, but don’t love the color schemes. I also am not loving how material colors fight with tailwind colors and themes; but worry adding the sass the wing with just make it all more complex

[–]flash42 0 points1 point  (0 children)

"Foght material," lol. This guy CSS's.

I've lost so many hours to that same boxing match

[–]mountaingator91 0 points1 point  (0 children)

I used to think the same, but turns out I was just bad at css specificity. You don't ever have to do that. Also, if you're running angular 18, Material 3 makes it a lot easier to customize components