Heikki Hellgren
Heikki Hellgren
Here's another list with the latest changes to this PR, relates to #30188 ``` Processed 19007 files (1m 35.1s) (219 warnings) ✖ Found 145 circular dependencies! 1) packages/canon/src/index.ts > packages/canon/src/components/Checkbox/index.ts...
Excluded the type imports, rebased and now it's down to 87: ``` ✖ Found 87 circular dependencies! 1) packages/canon/src/index.ts > packages/canon/src/components/Checkbox/index.ts > packages/canon/src/components/Checkbox/Checkbox.tsx 2) packages/canon/src/index.ts > packages/canon/src/components/DataTable/index.ts > packages/canon/src/components/DataTable/DataTable.tsx >...
@freben rebased!
@Rugvip would it make sense to add mention about this RFC to the "Migrating to MUI5" documentation?
Throwing in my 2 cents: I agree that the migration path with MUI will be difficult in the future, and moving to its own design system makes a lot of...
Hi @cdedreuille, We are using (mostly) our own company's design system currently for in-house plugins with some mixing of MUI as it has components our own design system does not...
@cdedreuille thanks! I would still like the possibility of overriding complete components from the components layer. This of course would be totally up to the user that it works correctly...
@Rugvip thanks for this comment, I think people would be able to work without the API contract too; anyway, it's only necessary to validate the overrides when updating the Canon...
@cdedreuille I think the priority of component implementation doesn't matter that much. Unless you cannot replace MUI with Canon completely, the move on top of Canon completely is impossible. Of...