-
Notifications
You must be signed in to change notification settings - Fork 47
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
Unexpected token type: 44(IMPORT_SYM) for @import #59
Comments
Same problem when processing the following less:
|
That is weird, I'm getting different error with the first file. Is is a full file? The error suggests that the character 1 of line 1 should have Beginning of error report I get with less4j-0.0.7.jar:
I tried that file also with less.js-1.3.1 and I get this:
Both seem to crash on the line 9 which contains this I can not explain the error you are getting on the first input (I will have another look on it tomorrow). |
I'm using using these less files to test how the less4j behaves when comparing to less.js. The idea is that when being compiled with less.js, the same content is processed to a valid output.... Can provide you with more details if needed... |
The second file also returns different error for me:
This is valid less but less4j crash for three reasons:
is supposed to be mixin definition. I can fix them either in 0.0.8 or 0.0.9. |
Which version of less.js do you use? |
Now I see That syntax is not implemented in less4j, what it does? I think I'm going to split this issue into three smaller issues so it is less confusing. I still can not explain the import error :( Edit: OK, I made mistake, I copy pasted expected output instead of input for testing. It is too late. |
Sorry for previous comments, I see the error now. The problem with first input is the line |
Update after less4j-0.0.8: both cases produce css output without errors or warnings. The first case still does not produces expected output due to missing color functions #16 . Second case produce following:
Tested with command line version. |
The first case now produces output similar to less.js. There is only one difference: Closing since all required issues are either closed or will be closed in the next release. |
When processing the following less using latest less4j version (0.0.7)
I get the following exception:
Expected output:
The text was updated successfully, but these errors were encountered: