Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Mixin return values

See original GitHub issue

Can I set a return value as a color? As in:

.myselector {
   border: 1px solid .custommixin(@colorValue);
}

Just wondering in response to another user’s issue regarding color functions: https://github.com/cloudhead/less.js/pull/488

Issue Analytics

State:
Created 12 years ago
Reactions:13
Comments:59 (41 by maintainers)

Top GitHub Comments

2reactions

matthew-deancommented, Mar 29, 2017

@distransient There has been more in-depth discussion around designing solutions for this in: https://github.com/less/less-meta/issues/16.

(Less-meta is a repo for higher-level goal planning for Less.js, rather than individual issues or bug reports.)

2reactions

seven-phases-maxcommented, Apr 12, 2014

Mixins are mixins, we must not conflate their usage with functions.

The problem is that there’s no way to forbid using mixins as functions. It is possible to use one as the other and they (and me 😃 get to use that ability. So de facto it’s only a matter of syntactic sugar and verbosity:

.sum(@a, @b) {
    @-: (@a + @b);
}

usage {
    width: @-;.sum(20px, 33px);
}

Using same “function” twice in the “same scope”:

// short (since 1.6.2):
usage {
    & {width:  @-;.sum(55px, 77px)}
    & {height: @-;.sum(11px, 99px)}
}

// oldschool (since 1.4.x):
usage {
    .-() {width:  @-;.sum(20px, 33px)}
    .-() {height: @-;.sum(40px, 42px)}
    .-();
}

Is there a reason to invent some new “Less function declaration/definition” syntax (different from a mixin definition syntax) only to not allow to use width: .sum(20px, 33px); directly?