Marshall Bowers
e5b6194914
This PR fixes an issue introduced in #25530 that broke the notifications that inform the user that a Zed update is required to continue using edit prediction. The issue is that the `Workspace` stored on the `Editor` is set _after_ the point we initialize Zeta, so capturing the `Workspace` at construction time leads to it being `None`. @ConradIrwin suggested that we could obtain the `Workspace` from the `Window`, which does indeed do the trick. I tested it both with and without this change by mocking the error response, like so: ```rs let response: Result<PredictEditsResponse, anyhow::Error> = Err(anyhow!(ZedUpdateRequiredError { minimum_version: SemanticVersion::new(0, 1, 0), })); ``` Release Notes: - N/A
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.