-
Notifications
You must be signed in to change notification settings - Fork 22
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
False error in comments #171
Comments
Thanks for the bug report! This is actually a diagnostics error. We'll try to fix it as soon as we can, unfortunately because we plan on updating the diagnostics code it's currently not on my personal priority list. If it's an easy fix, I might look into it when I find the time. But if anyone wants to, feel free to make a PR :) |
Would it be simple enough if it was checked to see if it was part of a string before giving an error? |
Yes, but the problem stems from how the 'is it part of a string check' is performed. We need to parse the code using regex expressions. We already have the correct regex expressions in the syntax highlighter, it's just not correct in the diagnostics class. It'd be a matter of copy pasting the correct expression. The plan is to improve this process as soon as the code parser is fully functional. |
Actually it doesn't appear possible to solve the current example currently. Your "checkStrayDollarSigns" function is fed line by line. In the example |
Extension version
2.1.1
Issue description
False error in comments
Scope inspector screenshots
Code
The text was updated successfully, but these errors were encountered: