Skip to content

maybe some bug in less 3.0.1 #3195

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

Closed
lialosiu opened this issue Mar 30, 2018 · 0 comments
Closed

maybe some bug in less 3.0.1 #3195

lialosiu opened this issue Mar 30, 2018 · 0 comments

Comments

@lialosiu
Copy link

sorry for my poor English.... m(_ _ )m

this less (just an example):

@cols: 1, 2;

.a(@i: length(@cols)) when (@i > 0) {
  @divider: e(extract(@cols, @i));
}
.a;

.b(@j: 1) when (@j < length(@cols)) {
  @divider: e(extract(@cols, @j));
}
.b;

will cause exception in less 3.0.1
image

but in less 2.7.3, run so far so good.
image

maybe some bug at here?
exception throwed in this line:

current = current.slice(length + parserInput.i - mem + curr);

because current is a number value 2:

image

any solution?

matthew-dean added a commit to matthew-dean/less.js that referenced this issue Jun 2, 2018
matthew-dean added a commit that referenced this issue Jun 16, 2018
matthew-dean added a commit that referenced this issue Jun 17, 2018
This reverts commit 468b532.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants