Replies: 1 comment 6 replies
-
I marked this as a bug at first, until I read it a little more carefully and yeah, this is more like a feature request. Returning a mixin body to assign to a property is undefined behavior. |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a mixin called
rgbify
, as seen below:It can be used as
color: #rgbify(#fff)[];
, and note the[]
to capture the return value(s). Without the[]
(just#rgbify(#fff)
), Less outputs[object Object]
as the value for wherever the mixin is used. I most definitely did not mean to have the value be[object Object]
, and I'm hoping Less could error when it encounters a value like that - otherwise i have no good way of knowing I missed it if I'm not looking carefully/specifically for that mistake.Beta Was this translation helpful? Give feedback.
All reactions