Tom HouléandMarshall Bowers
93ead966c2
Add StreamEnded variant so the client can distinguish between a stream that the cloud ran to completion versus one that was interrupted (see CLO-258). **That logic is to be added in a follow up PR**. Add an Unknown fallback with #[serde(other)] for forward-compatible deserialization of future variants. The client advertises support via a new x-zed-client-supports-stream-ended-request-completion-status header. The server will only send the new variant if that header is passed. Both StreamEnded and Unknown are silently ignored at the event mapping layer (from_completion_request_status returns Ok(None)). Part of CLO-264 and CLO-266; cloud-side changes to follow. Release Notes: - N/A --------- Co-authored-by: Marshall Bowers <git@maxdeviant.com>
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).
Other platforms are not yet available:
- Web (tracking issue)
Developing Zed
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.
Sponsorship
Zed is developed by Zed Industries, Inc., a for-profit company.
If you’d like to financially support the project, you can do so via GitHub Sponsors. Sponsorships go directly to Zed Industries and are used as general company revenue. There are no perks or entitlements associated with sponsorship.