-
Notifications
You must be signed in to change notification settings - Fork 5
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] Minor syntax highlighting issue #33
Comments
Saw this again. Seems like function types have their |
BTW -- if you make this project sponsorable I'll throw you a sponsorship. I use this daily. |
Thanks for the vote of confidence – it really means a lot! I apologize for not responding to this issue sooner, but I had a busy summer and now Nova 10 is coming in hot with Tree Sitter as its parsing engine. The good news is that many folks better than me at this sort of thing have written a Tree Sitter grammar so glaring issues like this should be rarer. I'm currently working on connecting the Tree Sitter syntax tree to Nova theme selectors and symbols. Nova 10 will likely show up before I'm ready, but I hope to follow its release shortly. |
Ahh nice. Sounds like it'll make your job easier since you'll just have to worry about the rust language server stuff. Your plugin still works better than Rust for VSCode which is crash city when using |
Please let me know if this is still an issue in the latest version (if you're still using this extension). Thanks! |
Describe the bug
There's a minor syntax highlighting issue with the use of function generic parameters like Fn() and FnOnce().
To Reproduce
See attached screenshot for an example. Note that the highlighter reverts to white and basically stops highlighting until something resets it inside the function.
Expected behavior
Correct syntax highlighting.
Screenshots
![Screen Shot 2022-08-23 at 6 14 57 PM](https://user-images.githubusercontent.com/591635/186275843-1b2c5695-770d-4f7d-a83e-e39c10059527.png)
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: