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 pattern of passing a css output to a value in another css does not work in Compiled, but it also does not fail type-checking. There only way to determine this doesn't work is by trying it. This could be problematic in migration from another CSS-in-JS library primarily.
I did not test this with styled.div({ '&:hover': styles1 });, but I expect it might not work as well. It does not throw a type error.
To Reproduce
[tested in a local Storybook, I have no codesandbox or anything, sorry]
Expected behavior
This works in Emotion and almost certainly in the tagged template expression interpolations in Compiled, but I'd vote that we don't want to support it in Compiled, and instead should just have a type error.
The text was updated successfully, but these errors were encountered:
Describe the bug
The pattern of passing a
css
output to a value in anothercss
does not work in Compiled, but it also does not fail type-checking. There only way to determine this doesn't work is by trying it. This could be problematic in migration from another CSS-in-JS library primarily.I did not test this with
styled.div({ '&:hover': styles1 });
, but I expect it might not work as well. It does not throw a type error.To Reproduce
[tested in a local Storybook, I have no codesandbox or anything, sorry]
Expected behavior
This works in Emotion and almost certainly in the tagged template expression interpolations in Compiled, but I'd vote that we don't want to support it in Compiled, and instead should just have a type error.
The text was updated successfully, but these errors were encountered: