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
The above code results in unexpected behavior since hoverStyles generates its own class name, which is independent from Button and therefore also independent of the Button components nested usage of the mixin.
MVP:
Display a clear error message when users attempt to use mixins in unsupported contexts, such as media queries or nested structures.
Caution
next-yak currently does not allow mixins to be used directly within media queries or nested structures
Inline mixin:
If doable we should probable add support for nesting mixins directly within a component, enabling constructs like the following:
Currently, next-yak lacks support for nesting mixins within media queries and nestings.
Problem:
The above code results in unexpected behavior since
hoverStyles
generates its own class name, which is independent fromButton
and therefore also independent of the Button components nested usage of the mixin.MVP:
Display a clear error message when users attempt to use mixins in unsupported contexts, such as media queries or nested structures.
Caution
next-yak currently does not allow mixins to be used directly within media queries or nested structures
Inline mixin:
If doable we should probable add support for nesting mixins directly within a component, enabling constructs like the following:
Additional Considerations:
We might add support for mixins which are imported from
.yak
files e.g.:The text was updated successfully, but these errors were encountered: