Open matthew-dean opened 9 months ago
I feel like the section on mixins implies that mixins, at the least, must:
Always have the same named parameters
Note that this appears to only be true in the case of named parameters, which is more related to #2
.
To reproduce:
In the docs, it describes how mixins match on arity (number of arguments).
That is, you can do this:
This will produce:
However, if you add a default value to the first parameter, like so:
... then you get the error:
wrong number of arguments for .mixin (1 for 2)
Expected behavior:
I would expect this to still match the first mixin by arity.
Something else that's unexpected is that you can't match the second mixin by arity by doing this:
However, the Less docs don't sufficiently explain (IMO) what the expected behavior should be in that case. Technically, there is a mixin that matches, but it's not clear from the Less docs if overloading mixins means you can "pass over" mixins with only one named argument. I'm really not sure what the behavior should be because the docs don't say, so I'd welcome opinions.
Environment information:
Latest Less / Node 16