Make it UI library agnostic

[luigi-derson]

Feature request

It would be a good idea to don't have Material UI library dependency. This way you can use a different library or your own one.

Is your feature request related to a problem? Please describe.

Not really, but I think not everyone likes Material design to say something 😅

Describe the solution you'd like

export core functionalities as utils, hooks, higher order functions and only the logic you have used on your customised components. These changes involves to have new section in the docs as well.

Describe alternatives you've considered

Additional context

This proposal comes out from creating custom components using Chakra UI for a personal project so I've cloned the project and I've been making the modifications to remove material UI dependency.

[s-c-p]

Hi @luigi-derson since the naming convention of UI elements is not consistent (e.g. top modal vs drawer) I am not sure if implementing such a feature would be straightforward. Do you have any ideas on how to bridge such deviations in code? And who should we respect when giving default names?

[luigi-derson]

Hi @luigi-derson since the naming convention of UI elements is not consistent (e.g. top modal vs drawer) I am not sure if implementing such a feature would be straightforward. Do you have any ideas on how to bridge such deviations in code? And who should we respect when giving default names?

Hi,

So the idea is to export only hooks, functions or higher order components to use with your chosen UI library. This way you would only have to import the logic and use it in your components.