I need support for tailwind.config.js editing because the concept is based on just installation and use. You are editing Tailwind Config Manually and it may be hard For Python Developers. It means you must paste tailwind.config.js lines every time you install the package to ensure the component library works.
Adding something like a tailwind config updater function may reduce extra efforts so anyone can wrap out any UI library based on the tailwind and install and use it.
It takes all tailwind configs from individual reflex-wrapped components merges them into a dictionary (union) and exports them to tailwind.config.js in .web as translated dictionaries to javascript objects.
I need support for tailwind.config.js editing because the concept is based on just installation and use. You are editing Tailwind Config Manually and it may be hard For Python Developers. It means you must paste tailwind.config.js lines every time you install the package to ensure the component library works.
Adding something like a tailwind config updater function may reduce extra efforts so anyone can wrap out any UI library based on the tailwind and install and use it.
It takes all tailwind configs from individual reflex-wrapped components merges them into a dictionary (union) and exports them to tailwind.config.js in
.webas translated dictionaries to javascript objects.