43061b6b16
Closes #ISSUE Adds a couple functions to the `SettingsStore`: - `get_value_from_file`: Gets a value from a given settings file (`Local`, `User`, etc) and if the value isn't found in the requested file, walks the known settings files in the order in which they are merged to find the settings value in lower precedence settings files (i.e. if value not set anywhere will always return default value) - `get_overrides_for_field`: Returns a list of settings files where a given setting is set that have higher precedence than the passed in file. e.g. passing in user will result in project settings files where the value is set being returned. Additionally changes the default for the `project_name` setting to uphold the rules we are attempting to enforce on the settings, namely: - All settings fields should be of the form `Option<T>` - `None` (or `null` in JSON) should never be a meaningful value Follow up PRs will handle implementing a function to write to an arbitrary settings file, and passing through metadata to the above functions to control how overrides are determined for more complicated cases like `SaturatingBool` (`disable_ai`) and `ExtendingVec` Release Notes: - N/A *or* Added/Fixed/Improved ... --------- Co-authored-by: Ben Kunkle <ben@zed.dev> Co-authored-by: Anthony Eid <hello@anthonyeid.me> Co-authored-by: Danilo Leal <daniloleal09@gmail.com> Co-authored-by: Anthony <anthony@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.