Antonio Scandurra
90c2da4dec
Refs https://github.com/zed-industries/zed/pull/4131 Refs https://github.com/zed-industries/community/issues/2415 Previously, when a view cache miss occurred during paint, we would either use the element produced during layout or create a new, detached node layout node. In both cases, we would issue a call to `draw`. The problem with this approach, however, is that `draw` would always paint the element at the given `bounds.origin`, which was required when the layout node was detached but harmful when the element was already embedded in the layout tree and already knew its bounds. In this second case, in fact, it was as if we were positioning the element "twice", which caused content to jump. Release Notes: - N/A
🚧 TODO 🚧
- Add intro
- Add link to contributing guide
- Add barebones running zed from source instructions
- Link out to further dev docs
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Developing Zed
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.