less / less/less.js

Can't apply mixin as varible from a namespace

Open
#3,406 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

consider closing feature request needs decision
Dominant language
JavaScript
Stars
17k
Forks
3.4k
Avg merge
7h 42m
Merged PRs (30d)
26

Description

This might be related to https://github.com/less/less.js/issues/3405:

.mix (@n) {
  value: @n;
}

@var: .mix(var);

#lookup {
  @var: .mix(lookup);
  @bar: bar;
}

.example {
  @var();
  value2: #lookup[@bar];

  // This is what I'm trying to do, since the above works:
  #lookup[@var]();
}

Expected:

.example {
  value: lookup;
  value2: bar;
}

Actual: unexpected token.

In this case I can't find a workaround using detached rulesets, but since @var() works I expect the nested syntax #lookup[@var]() to work as well.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the LESS snippet and comparing the generated CSS with the expected output. Trace how namespace lookup and variable mixin calls are parsed, then add coverage in the relevant existing test area. Done means #lookup@var compiles and produces the expected value declaration.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
compilers
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.