| Age | Commit message (Collapse) | Author | Lines |
|
Ensure that all the fields that rust-analyzer understands are in the
manual, they all have doc comments, and they use consistent
punctuation (`;` rather than mixing `,` and `;`).
Whilst we're here, fix the `sysroot_src` example and add 2024 as a
legal value for Rust edition.
|
|
|
|
|
|
|
|
|
|
|
|
feat: add `toggleLSPLogs` command
Implement client-side command to toggle LSP logs in VSCode.
The command replaces the need to add/remove the `"rust-analyzer.trace.server": "verbose"` setting each time one wants to display logs. I've also updated the docs/ instances that reference the now outdated manual method.
The command labeled `rust-analyzer: Toggle LSP Logs` enables the setting project-wide and opens the relevant trace output channel.
Closes #8233
|
|
add `toggleLSPLogs` command
update docs to reflect new command
|
|
To generate all the requisite files, you need to run `cargo xtask codegen` not
`cargo test -p xtask`.
|
|
|
|
The manual has been linking to the repo
https://github.com/rust-analyzer/rust-project.json-example/tree/master
This repo does not contain a rust-project.json, does not appear to have _ever_ contained a rust-project.json, and my bug report about this has gone untouched: https://github.com/rust-analyzer/rust-project.json-example/issues/4
Since I can't figure out an example, this commit removes the link pending better documentation.
|
|
|