9f7987c532
Closes https://github.com/blopker/codebook/issues/79 Recently, the setting `diagnostics_max_severity` was changed from `null` to `warning`in this PR: https://github.com/zed-industries/zed/pull/30316 This change has caused the various spell checking extensions to not work as expected by default, most of which use the `hint` diagnostic. This goes against user expectations when installing one of these extensions. Without `hint` as the default, extension authors will either need to change the diagnostic levels, or instruct users to add `diagnostics_max_severity` to their settings as an additional step, neither of which is a great user experience. This PR sets the default `hint`, which is closer to the original behavior before the aforementioned PR. Release Notes: - Changed `diagnostics_max_severity` to `hint` instead of `warning` by default --------- Co-authored-by: Kirill Bulatov <kirill@zed.dev>
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.