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
In vscode struct and enum type names have a textmate scope, but field types don't have a different textmate scope and so can't be styled differently from the default 'source.rust' textmate scope.
This level of styling fidelity is obviously essential for opening up the ability for people to roll their own rusty cyberPunk themes. (btw. mutation being underlined seems very cyberpunk)
but I can't see any sign of the entity.name.field textmate style on any fields (used or defined)? It feels like there should be enough to style fields separately from their types.
Any tips gratefully received!
The text was updated successfully, but these errors were encountered:
Thank you for the proposal! Our current code highlighting setup is quite handcrafted, so instead we would like to invest resources into the development of semantic tokens highlighting API (#3159) that should reach the stable language server protocol release in the nearest future.
In vscode struct and enum type names have a textmate scope, but field types don't have a different textmate scope and so can't be styled differently from the default 'source.rust' textmate scope.
This level of styling fidelity is obviously essential for opening up the ability for people to roll their own rusty cyberPunk themes. (btw. mutation being underlined seems very cyberpunk)
I can see there's a mapping from TAG_TO_SCOPES here:
https://github.com/rust-analyzer/rust-analyzer/blob/04dacb994349848873f9b2576d53685630883300/editors/code/src/highlighting.ts
and digging there is a field tag:
https://github.com/rust-analyzer/rust-analyzer/blob/27587f3501168c0522e62bf14923aedbdc08a960/crates/ra_ide/src/syntax_highlighting.rs
but I can't see any sign of the entity.name.field textmate style on any fields (used or defined)? It feels like there should be enough to style fields separately from their types.
Any tips gratefully received!
The text was updated successfully, but these errors were encountered: