The main reason why I'm opening this draft PR is to use it as a personal backlog.
What I'm aiming at with this is to both expand all the sizing declarations as well as handling them dynamically within each component.
In my point of view the developer that uses the library should be able to use all the sizes available from Tailwind CSS (from size-0 all the way up to size-96), either by changing the class of the root element or using a size prop.
Roadmap
firstly test each component, one by one, to check if this is applicable to all of them
define what to do for those components that aren't square and have different widths and heights (which one should be controlled? should it depend on component type?)
define how to handle nested components (both from the library and user's created)
⚠️ Highly experimental PR!
The main reason why I'm opening this draft PR is to use it as a personal backlog. What I'm aiming at with this is to both expand all the sizing declarations as well as handling them dynamically within each component.
In my point of view the developer that uses the library should be able to use all the sizes available from Tailwind CSS (from
size-0
all the way up tosize-96
), either by changing the class of the root element or using asize
prop.Roadmap
width
s andheight
s (which one should be controlled? should it depend on component type?)