This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Less syntax highlighting inline variables in curly braces is missing. In picture, @{lightblue} is a variable as well as @{buttonColor} Keep up the great work with web workbench! Whoops, looks like there is a bug in there too. Bad caching I suppose. This code:
Does NOT compile properly. All versions of the culprit are compiled the same. However this same code compiled through other compilers work as they should. |
|
|
What version of Web Workbench are you running? This is compiling for me here. If possible could you update (the latest version in the Gallery should be fine) and retry this. e.g. My output for the above is:
In regards to the variable highlighting, we are not attempting to highlight these, we are just treating the whole of "progid:DXImageTransform.Microsoft.gradient(startColorstr='@{culprit}', endColorstr='@{culprit}');" as the value for the property for the purposes of highlighting.
|
|
|
Hello Jeremy, I get the same output through workbench but this is a bug, and I do have the latest version. If you try it for example HERE you can see the output should be:
|
|
|
Ah, sorry I missed that from your original post. Understand now. We execute the actual Less parser under the covers for compilation so presumably there has been an update which has fixed this. I will have a look into that and let you know once we have an update available.
|
|
|
Ive had a look at this and grabbing the current official Less source and parsing this via the command line yields:
So my suspicion would be that LessPhp has their own compiler implementation which treats this differently. Your best bet would be to raise this as an issue with Less (https://github.com/cloudhead/less.js/issues) - we track along with the Less releases so once its fixed there we will be able to pick it up.
|
|
|
Thank you for the attention Jeremy, I will continue this on github then! |
|