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

[BUG] Broken syntax highlighting after some comments #29

Open
SpontanCombust opened this issue May 5, 2024 · 2 comments
Open

[BUG] Broken syntax highlighting after some comments #29

SpontanCombust opened this issue May 5, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@SpontanCombust
Copy link
Owner

Some keywords break syntax highlighting when being at the end of a single line comment.

How to reproduce:

  1. Start writing a single line comment with //
  2. At the end of the comment write one of the following: var, autobind, hint or default. Don't write anything after that.
  3. After this some portion of code after the comment should appear to be highlighted like a variable
@SpontanCombust SpontanCombust added the bug Something isn't working label May 5, 2024
@SpontanCombust
Copy link
Owner Author

The bug can be observed in 1.21 version of types.ws after line 1144

@SpontanCombust
Copy link
Owner Author

Regex that can be used to find bug cases:
//.*(var|autobind|default|hint)$

@SpontanCombust SpontanCombust added this to the v0.3.0 milestone May 9, 2024
@SpontanCombust SpontanCombust removed this from the v0.3.0 milestone May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Development

No branches or pull requests

1 participant