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 exposing classList as a prop requires a custom type. It would be better to create a "ClassList" type definition, use that everywhere and expose it. PR following shortly.
The text was updated successfully, but these errors were encountered:
We are in the process of meditating if classList should be deprecated, replaced by something else (such a super powered class[class behaving as classlist]/clsx equivalent) or just plainly suggest to use clsx instead, or maybe even leave it as is.
It has issues like defining both class and classList overwrites each other in un/predictable ways when stuff is dynamic. Specially when used in spreads(spreading before or after setting class as attribute?), when effects run out of the expectedorder(there are no expectation on the order effects run), and it has issues with SSR too.
I am probably missing some other situation. I meant to investigate this. While I somewhat understand the issue, I am not confident enough about its problems (it only happens in some circumstances and most of the time is not an issue or a big deal), and I am also not authoritative enough to decide over its future.
Currently exposing classList as a prop requires a custom type. It would be better to create a "ClassList" type definition, use that everywhere and expose it. PR following shortly.
The text was updated successfully, but these errors were encountered: