Skip to content
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 error in expr_ext.rs #450

Closed
1 task done
arendjr opened this issue Sep 29, 2023 · 1 comment · Fixed by #452
Closed
1 task done

🐛 Unexpected error in expr_ext.rs #450

arendjr opened this issue Sep 29, 2023 · 1 comment · Fixed by #452
Assignees
Labels
A-Linter Area: linter L-JavaScript Language: JavaScript and super languages S-Bug-confirmed Status: report has been confirmed as a valid bug

Comments

@arendjr
Copy link
Contributor

arendjr commented Sep 29, 2023

Environment information

Just received the following error from Biome in my console:


This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates/biome_js_syntax/src/expr_ext.rs:633:26
Thread Name: tokio-runtime-worker
Message: begin <= end (1 <= 0) when slicing `/`

What happened?

I was simply working in VS Code with the extension enabled and typed // to start a new comment.

Expected result

It should not error.

Code of Conduct

  • I agree to follow Biome's Code of Conduct
@Conaclos Conaclos self-assigned this Sep 29, 2023
@Conaclos Conaclos added A-Linter Area: linter L-JavaScript Language: JavaScript and super languages S-Bug-confirmed Status: report has been confirmed as a valid bug labels Sep 29, 2023
@Conaclos
Copy link
Member

As a temporary fix, I recommend disabling noControlCharactersInRegex.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Linter Area: linter L-JavaScript Language: JavaScript and super languages S-Bug-confirmed Status: report has been confirmed as a valid bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants