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
Currently, this results in the class being ultimately set to "child [:parent :grandparent]".
So the users have to use r/class-names every single time they need to combine classes:
Another problem with that approach is that the data is composed prematurely. When the "stringification" happens at the very edge of the rendering, the user code can still the full :class data structure as it was created by the app, including all the collections, keywords, strings, nils. Seeing that definitely helps with debugging. It also enables class collection preprocessing in some child component, although I'm hesitant do deem this particular usage as viable.
The text was updated successfully, but these errors were encountered:
An example of what IMO the usage should end up with:
Currently, this results in the class being ultimately set to
"child [:parent :grandparent]"
.So the users have to use
r/class-names
every single time they need to combine classes:Not too harde but harder than it can be.
Another problem with that approach is that the data is composed prematurely. When the "stringification" happens at the very edge of the rendering, the user code can still the full
:class
data structure as it was created by the app, including all the collections, keywords, strings,nil
s. Seeing that definitely helps with debugging. It also enables class collection preprocessing in some child component, although I'm hesitant do deem this particular usage as viable.The text was updated successfully, but these errors were encountered: