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
DX regression in view macro for rust-analyzer 2024-03-18 (v0.3.1885) and newer #2527
Comments
Yeah, I've noticed this as well. Highlighting any part of the
|
I also had the same problem.. I tried some ways to ignore clippy (because when it hovers that's what appears), but I couldn't. |
same, didn't have much luck with any allow or config options and it also seemed to bork the syntax highlighting in vscode a tad too - primarily that the Component name lost it's coloration after rust-analyzer finished indexing leptos. Confirmed that reverting |
I don't know the first thing about how rust-analyzer works. Is there a reason to think this was an intentional decision by rust-analyzer, not a bug/regression? If it was an intentional decision to no longer support overlapping spans in this way, then I guess we should revert the changes made in #2289. If not, opening an issue there makes sense and @Ar4ys I'd appreciate it if you could do that, as you know what you're talking about more than I do! |
While trying to make a reproduction repository for my issue against rust-analyzer, I found out that DX regressions are not present when using latest stable rustc ( Still investigating why nightly breaks.... |
confirming downgrading rust-analyzer to Regression present on Span shows on LSP hover:
Appreciate the workaround and notes on this |
In rust-analyzer 2024-03-18 (v0.3.1885) they updated how they handle overlapping spans, which resulted in a degraded DX of #2289 (worse syntax highlighting, hover tooltips, go to definition etc.).
Examples
Note: This is not a full list of regressions
Hover over items used inside
view!
macroComponent's syntax highlighting
Go to definition
Temporary workarounds
Until the issue is resolved, users can:
rustc 1.78.0 (9b00956e5 2024-04-29)
at the time of writing), instead on nightlyProposed solutions
I see two possible solutions to this issue:
view!
macro.The text was updated successfully, but these errors were encountered: