-
-
Notifications
You must be signed in to change notification settings - Fork 250
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
Comments
They are aware of the need for documentation; see less/less-docs#13 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? |
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. |
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? |
No, the compiler only ships in WE. The editor is in VS |
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). |
Yes. That means the preview pane, and the generated (note that WE does add lots of validations & IntelliSense features to the LESS & CSS editors) |
Yes |
Too bad it wasn't an email revealing the release date of the Xbox One... On Wed, Aug 28, 2013 at 3:11 PM, SLaks [email protected] wrote:
Kamran Ayub |
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.
The text was updated successfully, but these errors were encountered: