Doods
e26bb05567
As-salamu alaykum, [I recently started suffering from the same issue as this user](https://users.rust-lang.org/t/rust-analyzer-checkonsave-command-works-but-shows-invalid-config-warning/128652), which is caused by something the docs of Zed promote, so I decided to help fix it. >[anutrix](https://users.rust-lang.org/u/anutrix) > When I add "rust-analyzer.checkOnSave.command": "clippy" I get: > > invalid config value: /checkOnSave: invalid type: map, expected a boolean; > Extension Info: Version 0.3.2433, Server Version 0.3.2433-standalone (66e3b5819e 2025-04-21) > and in Language Server logs: > > [Error - 3:26:22 AM] Server process exited with code 0. > Clippy works fine but these warnings stays and extensions shows yellow/unstable in VSCode: > > Additionally, if I replace > > "rust-analyzer.checkOnSave.command": "clippy" > with > > "rust-analyzer.checkOnSave": true, > "rust-analyzer.checkOnSave.command": "clippy" > [jplatte](https://users.rust-lang.org/u/jplatte) > From the documentation, it seems like rust-analyzer.checkOnSave.command does not exist. It should be rust-analyzer.check.command.
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS and Linux you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- Windows (tracking issue)
- Web (tracking issue)
Developing Zed
- Building Zed for macOS
- Building Zed for Linux
- Building Zed for Windows
- Running Collaboration Locally
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.