Hmmm, I don't see ability to handling nested selectors for Mixins in Less.

.mixin(@a: 1, @b) { content: @a + @b; }; .| // SimpleSelector
.mixin(@a: 1, @b) { content: @a + @b; }; .test { .|} // Declarations
.mixin(@a: 1, @b) { content: @a + @b; }; .test { .| // Nothing

In case with Declarations we need determinate property before/after, property value and more specific case:

.test {
  color: #fff;
  .|
  content: 123;
}

@mrmlnc Thank a lot!
I had recreate the commit to merge the changes. Also I made a few (mostly cosmetic) changes.

@aeschli,

Yeap, that's good 👍. But what to do with Mixins in Less? We have three contexts and one of them does not exist in the AST.

In my plugins I use the current string for comparison textBeforeCurrentWord because AST may not have Node for the current word.

For LESS we need to override 'parseRuleset' to detect rulesets with selectors that are valid mixin declarations and annotate the selector identifier.
On the reference side, we get MixinReference Nodes already for .abc and #abc. What is the 3rd context?

Now AST contains all Mixins in the Less file. Sorry, I was not entirely correct.

The problem is that Mixin can be called in different contexts:

1. SimpleSelector

.mixin() {}
.m|

2. Declarations

.mixin() {}
.test {
  .m|
}

3. Just case, not context. Here getNodeAtOffset returns null.

.mixin() {}
.test {
  .m|
// without }

Also, the problem is that we cannot determine: MixinReference before us or Selector. Because the selector becomes MixinReference only when I add ().