You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just updated to the latest RA version and am now getting these hints:
macro-error: ::leptos::leptos_dom::tracing::instrument: proc-macro is explicitly disabled
macro-error: tracing::instrument: proc-macro is explicitly disabled
macro-error: server: proc-macro is explicitly disabled
Which is because I told it not to expand instrument and server macros. Since they just wrap the code, this allows RA to treat them as no-op and it helps with completion inside them, performance etc.
I'm fine with this hint existing, but I personally don't want it because it I use this in a lot of places and it creates a lot of noise. Unfortunately the only way I've found to disable it is to disable the macro-error diagnostic which seems overly broad and I'm afraid I'll miss other important macro errors.
There should probably be a way to disable that hint specifically. I'm open to other solutions too though, e.g. if there's a way to disable just hints for macro-error.
The text was updated successfully, but these errors were encountered:
I just updated to the latest RA version and am now getting these hints:
Which is because I told it not to expand
instrument
andserver
macros. Since they just wrap the code, this allows RA to treat them as no-op and it helps with completion inside them, performance etc.I'm fine with this hint existing, but I personally don't want it because it I use this in a lot of places and it creates a lot of noise. Unfortunately the only way I've found to disable it is to disable the
macro-error
diagnostic which seems overly broad and I'm afraid I'll miss other important macro errors.There should probably be a way to disable that hint specifically. I'm open to other solutions too though, e.g. if there's a way to disable just hints for macro-error.
The text was updated successfully, but these errors were encountered: