-
Notifications
You must be signed in to change notification settings - Fork 230
pre-announcement of changes to LESS syntax #169
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
Comments
Hey @braver, thank you very much for reaching out proactively, highly appreachiated. I'm currently trying to find the best team member(s) to discuss this with you (I'm not one of those., for sure) - can you give me a bit more info, since I don't clearly understand the scope of the change you are talking about:
Apologies for asking potentially stupid questions, just wanna wrap my head around the scope of this challenge so I know who to involve. |
@LinusBorg Hi, the vue syntax imports the LESS syntax via its scope. Basically what needs to be done is revert this commit: 2e8c5b9 |
Thanks, got it. |
Hi @braver that sounds good. Thank you for letting us know. Can you email me at [email protected] to schedule a time to make the switch? |
@skyronic I just tagged LESS 2.5.0 with the proposed changes. |
package control can need over an hour to catch the updates, I'll keep an eye on it. |
A few months ago a new version of LESS was released that changed the root selector to
source.css.less
. The intention at the time was to bring the syntax in line with CSS, and thereby make more extensions like autocompletion and key bindings work for both out of the box. It got us 95% of the way there, but the recursion in LESS (and SCSS for that matter) makes it impossible to get there completely. In essence, the CSS syntax, and therefore its autocomplete features, leans heavily on the fact that properties and selectors are each in their own neatly delineated spaces. This doesn't always work for LESS, and the way extensions are inherited doesn't leave us another option than making a clean break.So, I intend to release LESS 2.5 soon. It has important improvements that are only possible by moving a few steps away from the way the CSS package does things. It will also revert the root scope back to
source.less
. I would like to coordinate this release so that Vue users don't experience breakage again (sorry about last time!). If all goes well no-one has to notice anything. Perhaps we can pick a time and date to make the change?The text was updated successfully, but these errors were encountered: