You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
now that angular support tailwind out of the box, are all the apps should support tailwind if one of the shared lib using it?
I got glimpse of two things for using tailwind in angular
all the components that using tailwind should have their ViewEncapsulation.None
and the app should have a tailwind.config.json in its root.
It will be easy to do these changes, but what will happen if we want to write one of the shared lib with tailwind? to me tailwind is the opposite concept of component styling. a component that should wrap whatever style inside itself now become dependant of an external library that only available in the app. i'm not even sure how the storybook should be used in this case. or if the component testing will continue to work or not.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
now that angular support tailwind out of the box, are all the apps should support tailwind if one of the shared lib using it?
I got glimpse of two things for using tailwind in angular
all the components that using tailwind should have their
ViewEncapsulation.None
and the app should have a
tailwind.config.json
in its root.It will be easy to do these changes, but what will happen if we want to write one of the shared lib with tailwind? to me tailwind is the opposite concept of component styling. a component that should wrap whatever style inside itself now become dependant of an external library that only available in the app. i'm not even sure how the storybook should be used in this case. or if the component testing will continue to work or not.
Beta Was this translation helpful? Give feedback.
All reactions