Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
TedDriggs opened this issue Aug 15, 2013 · 8 comments

Comments

@TedDriggs
Copy link

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
Copy link
Collaborator

SLaks commented Aug 16, 2013

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
Copy link
Owner

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
Copy link

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
Copy link
Owner

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

@kamranayub
Copy link

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
Copy link
Collaborator

SLaks commented Aug 28, 2013

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
Copy link
Owner

Yes

@kamranayub
Copy link

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 [email protected] 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants