Teradata / covalent

Teradata UI Platform built on Angular Material
https://teradata.github.io/covalent/
MIT License
2.23k stars 359 forks source link

feat: framework agnostic components #1828

Closed ericis closed 1 year ago

ericis commented 3 years ago

Feature Request

Currently, it seems these components rely on Angular + Material. As a result, engineers must adopt Covalent + Material + Angular and keep them in sync over time to use a single component.

Would you consider a roadmap migration to something like StencilJS that can target native JavaScript, Angular, React, and Vue as a runtime? Then, a single Covalent component might run on all popular runtimes and only depend on some core node packages and tree shaking can always ensure minimal deployment size.

What is the expected behavior?

Using certain Covalent components...

What is the motivation / use case for changing the behavior?

Coupling the choice to use Covalent with Angular + Material...

Which version of Angular and Material, and which browser and OS does this issue affect?

All

Did this work in previous versions of Angular / Material?

Of course.

Other information

Great work!

owilliams320 commented 3 years ago

Hello @ericis thank you for feature request and comments. We have been taking great consideration into where covalent as a design system for enterprise is going. With that we should have some updates in works related very closely to this feature request!

DaSchTour commented 2 years ago

Instead of migrating to StencilJS (which was painful to use when I tried) it might be another option to create an angular elements build for other frameworks. I actually migrated from StencilJS to Angular Elements for one project.

ericis commented 2 years ago

https://open-wc.org/ and https://lit.dev/ are also options

owilliams320 commented 1 year ago

We are now publishing web components made from lit based off of MDC web components 🚀 🔥 https://github.com/Teradata/covalent/tree/main/libs/components