@margeeta I understand your point, but it seems a bit contradictory. Google, the creator of the Material Design Specification, also owns Flutter and Angular. So, it would be logical to provide something tailored for Angular (you've done so for Flutter).

The purpose of the tool is to simplify theme customization and then allow easy export for integration with underlying technologies. You've achieved this for Flutter, which is understandable. Similarly, not doing so for Swift also makes sense. However, not having a similar solution for Angular is puzzling.

While there is a generic CSS file, it often requires substantial modification to work properly with the underlying application or framework. Given that Angular Material is commonly used with Angular, it would be more practical to avoid a generic CSS file for any web app (which isn’t always the case) and instead support frameworks that are inherently based on Material Design (like Angular and Flutter). Angular Material see's this css file as an anti pattern. There is a very opinionated/specific way to setup theming in order for it to work properly and follow the Material Spec to the T.

In my opinion, not supporting an Angular Material specific export is a significant oversight.

Export for angular-material #38

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions