Update manual for inlay hint customization #11708
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closes rust-lang#6883 This functionality was changed as of rust-lang#11445 and now can be customized using native VSCode settings instead of `rust-analyzer`-specific ones.
|
|
||
| // Overrides for specific kinds of inlay hints | ||
| "rust_analyzer.inlayHints.foreground.typeHints": "#fdb6fdf0", | ||
| "rust_analyzer.inlayHints.foreground.paramHints": "#fdb6fdf0", | ||
| "rust_analyzer.inlayHints.background.chainingHints": "#6b0c0c81" |
There was a problem hiding this comment.
As far as I can tell, there is no equivalent for the chainingHints color available in VScode settings yet – they just use the base editorInlayHint.* colors.
There was a problem hiding this comment.
Ye the proposal only defines type and parameter hints, everything else will fall back to the general
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to #6405, #6883 but not sure if they should be closed or not as this is just a documentation update.
This functionality was changed as of #11445 and now can be customized using native VSCode settings instead of
rust-analyzer-specific ones.