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
|
I am having some strange behaviors in .less with Web Workbench (pro) newest release. I really don't know how to explain them, so I am just posting screenshots. They seem pretty random and almost arbitrary. All of these examples are from the .less files included in Metro UI CSS, and open source project you can find here : Here First one is that on some valid expressions, it just tells me they are invalid during the editor. The file compiles fine, and it works fine when run - but it is just obnoxious. I can find nothing wrong with the syntax and no logical reason it cannot understand it. The next one is that it just likes to not highlight fully some things; I can find no rhyme or reason for this. This is scattered all over the .less files in the project I linked and I'd love some explanations. It is not breaking, but my OCD just cannot abide it. (Please notice the last few letters of the word "helper" at the end of the selector definition list) The next one is that it just isn't liking some variable declarations; Again, they are perfectly valid and run fine, it just keeps giving me the squiggly of impending doom. I have no idea why. Likewise anywhere these variables are used they give me the same error - but again, it compiles fine. And then the next is that some things I suppose it considers 'mixins' are being registered as invalid, even though I have used the appropriate declarations (using the // ww-expect "colors.less" syntax)* - these are perfectly valid, and they again, compile fine. Another issue is that sometimes it just seems to like to keep highlighting from previous things, like this example using the @font directive. Take a look at the first few letters of the word @font... But that is not the craziest part. If I just do a few carriage returns, it goes away! This isn't the biggest issue in the world, but it confuses me and it is just a bit annoying. Look at how the formatting resumes normal behavior when I put in enough returns. |
|
|
This typically occurs when our parser is lagging behind on what is valid syntax. We incrementally update this as gaps are identified. I will have a look into these examples and look to make some updates to our parser with our next round of parser fixes which we will be making shortly and let you know once these have been updated in the nightlies.
|
|
|
We have added a new round of parser fixes into the nightlies which should address the issues you mentioned here. I have gone through the Metro library generally and fixed up a few things I noticed along the way. These updates will be available in the next nightly build (20121205) for you. Let us know if you continue to see any problems after installing the updated nightly.
|
|