LESS editor shows error for new :extend() syntax (compilation to CSS works)

[TedDriggs]

Less 1.4 adds a new :extend pseudoclass. Using it shows up as an error in the editor, but when compiled the statement works as expected.

Note: I can find almost no documentation about this pseudoclass. I'm trying to contact the LESS team to fix that.

[SLaks]

They are aware of the need for documentation; see less/less-docs#13
For now, you can read through less/less.js#1155 and similar issues.

To address your question, the LESS language service (including the parser & object model) was moved to VS itself as of 2012.2.

@madskristensen, is it remotely possible for us to extend the parser from within WE so we can add support for new language features before a full VS update ships?
Even with the new release schedule, the web still moves faster than VS.

[madskristensen]

No, unfortunately not. However, the CSS/LESS parser in VS 2013 can be replaced by extensions, but that is a lot of work. We're aiming for all the LESS parser issues to be solved in an update to VS2013. It won't make it in to the final RTM version.

[kamranayub]

So any LESS compilation issues are actually bugs with VS? Man, that's too bad, at least with an extension we can report and get them fixed reasonably fast... is there a place to report LESS compiler issues because I've found some when using WE?

[madskristensen]

No, the compiler only ships in WE. The editor is in VS

[kamranayub]

OK, so this is still the right place to report any compiler issues (if it's WE and not an issue with the less compiler itself).

[SLaks]

Yes.

That means the preview pane, and the generated .css files, but not the syntax highlighting and basic error checking of the LESS editor itself.

(note that WE does add lots of validations & IntelliSense features to the LESS & CSS editors)

[madskristensen]

Yes

[kamranayub]

Too bad it wasn't an email revealing the release date of the Xbox One...
that would have been much better.

On Wed, Aug 28, 2013 at 3:11 PM, SLaks notifications@github.com wrote:

@stwylie https://github.com/stwylie I think you replied to the wrong
email...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/43#issuecomment-23443675
.

Kamran Ayub