Components should adhere to feature principle regarding customization

[rbenzazon]

Package

v4.x

Description

I just created an app UI prototype, then I tried to create all the variant configuration to create a complete design system that uses variant and color attribute to apply these customization and make them reusable, I discovered that the variant and compoundVariant is optional in the codebase, some component have support for class and ui attribute but don't support variants, I find it very disturbing because I can't create a simple reusable variant and it will make the UI code messy and prone to design system escape. I would like to make it a rule that if any customizable is possible on class and/or ui, this must be supported in the variants as well.

Regards

Additional context

No response

[benjamincanac]

Would you mind being a bit more specific on what you're trying to achieve?