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
but there are situations where it would be convenient to pass/override the classes for ALL instances of a component (instead of having to do it for each one). This is specially useful since forwarding slots can have an unexpected issue with $$slot, making point 3 non-optimal.
Consider how best to support customizing styling at an app/global level (likely context)
It would be powerful to support passing any props (not just class / classes) for things like shrinkLabel, etc...
Need to decide on how this would work with per-variant styles. Maybe adding a variant-{name} class or `data-variant="name" attribute should also enable per-variant overrides:
Proposal
We already support:
text-accent-500
,bg-purple-500
, etc) usingtailwind.config.cjs
class
/classes
props to each component:global(.Button) { ... }
)variant="none"
but there are situations where it would be convenient to pass/override the classes for ALL instances of a component (instead of having to do it for each one). This is specially useful since forwarding slots can have an unexpected issue with $$slot, making point 3 non-optimal.
Consider how best to support customizing styling at an app/global level (likely context)
It would be powerful to support passing any props (not just
class
/classes
) for things likeshrinkLabel
, etc......this might be too challenging, so just setting
class
/classes
might have to suffice.Need to decide on how this would work with per-variant styles. Maybe adding a
variant-{name}
class or `data-variant="name" attribute should also enable per-variant overrides:Existing solutions
TODO
ComponentName
classes to all components with top-level componentvariant-*
classes when variant appliedclasses
property to improve sveld props display/** @type {{root?: string, icon?: string, loading?: string}} */
The text was updated successfully, but these errors were encountered: