Skip to content

rust_analyzer.inlayHints color properties are not allowed #11764

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

Closed
sgon00 opened this issue Mar 19, 2022 · 6 comments
Closed

rust_analyzer.inlayHints color properties are not allowed #11764

sgon00 opened this issue Mar 19, 2022 · 6 comments

Comments

@sgon00
Copy link

sgon00 commented Mar 19, 2022

Screenshot_20220320_013436

There is an existing closed bug: #4334

I can not re-open it, so I am opening another one here.

Basically, I just copied the official manual's JSONC codes to my settings.json. It doesn't work at all. VSCode will complain these properties are not allowed. (maybe does not exist at all).

I have no ideas why. Can anyone please let me know what's wrong with it?

Both VSCode (1.65.2) and rust-analyzer (releaseTag: 2022-03-14) are in the latest version. I am running debian 11.2.

@lnicola
Copy link
Member

lnicola commented Mar 19, 2022

See https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/user/manual.adoc#color-configurations and #11733.

@lnicola lnicola closed this as completed Mar 19, 2022
@sgon00
Copy link
Author

sgon00 commented Mar 19, 2022

@lnicola thank you very much for your help. The new way works.
Btw, should we keep the issue opened as a documentation (manual) bug?
This manual is wrong.

@lnicola
Copy link
Member

lnicola commented Mar 19, 2022

The manual has been updated (I linked to it), but it will be published on Monday. We usually close issues when they are fixed, not when the new version comes out.

@sgon00
Copy link
Author

sgon00 commented Mar 19, 2022

@lnicola ok, understand.
Hopefully, people can find this bug when they meet such problem before Monday.
I have spent 4 hours on this issue (nearly a day).

@lnicola
Copy link
Member

lnicola commented Mar 19, 2022

Sorry for that. If it happens again, feel free to ask right from the start (or look at the existing issues, they're generally reported multiple times).

@sgon00
Copy link
Author

sgon00 commented Mar 19, 2022

OK, got it. thank you very much for your quick answer and help. 😄👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants