zed/crates/assets/Cargo.toml

[package]
name = "assets"
version = "0.1.0"
edition = "2021"
publish = false
license = "GPL-3.0-or-later"

[lib]
path = "src/assets.rs"

[lints]
workspace = true

[dependencies]
anyhow.workspace = true
gpui.workspace = true
rust-embed.workspace = true
chore: Extract `assets` module out of zed crate. (#3957) This essentially shaves off about 10% off of an incremental build after project change and potentially more if you're changing stuff like `welcome` that's very close to the `zed` crate in the dep graph. That's because macro expansion takes place even in incremental builds it seems? And zed (lib) + zed (bin) could take up to 4 seconds out of an incremental build, which is a lot in a 10s build. In reality though it shaves 1 second off of 5 seconds incremental 'welcome'/ 1s off of 10s 'project' builds. Note that we had `assets` crate in the past (removed in #2575 /cc @maxbrunsfeld), but this is a bit different, because `assets` is a dependency of just zed and nothing else. We essentially cache macro expansion results ourselves. Release Notes: - N/A 2024-01-09 00:49:14 +03:00			`[package]`
			`name = "assets"`
			`version = "0.1.0"`
			`edition = "2021"`
Fix assets build 2024-01-09 02:53:01 +03:00			`publish = false`
Licenses: change license fields in Cargo.toml to AGPL-3.0-or-later. (#5535) Release Notes: - N/A 2024-01-27 15:51:16 +03:00			`license = "GPL-3.0-or-later"`
Remove license-file from Cargo.toml as it is apparently redundant (#4218) Release Notes: - N/A 2024-01-23 19:40:30 +03:00
New revision of the Assistant Panel (#10870) This is a crate only addition of a new version of the AssistantPanel. We'll be putting this behind a feature flag while we iron out the new experience. Release Notes: - N/A --------- Co-authored-by: Nathan Sobo <nathan@zed.dev> Co-authored-by: Antonio Scandurra <me@as-cii.com> Co-authored-by: Conrad Irwin <conrad@zed.dev> Co-authored-by: Marshall Bowers <elliott.codes@gmail.com> Co-authored-by: Antonio Scandurra <antonio@zed.dev> Co-authored-by: Nate Butler <nate@zed.dev> Co-authored-by: Nate Butler <iamnbutler@gmail.com> Co-authored-by: Max Brunsfeld <maxbrunsfeld@gmail.com> Co-authored-by: Max <max@zed.dev> 2024-04-24 02:23:26 +03:00			`[lib]`
			`path = "src/assets.rs"`

Move Clippy configuration to the workspace level (#8891) This PR moves the Clippy configuration up to the workspace level. We're using the [`lints` table](https://doc.rust-lang.org/cargo/reference/workspaces.html#the-lints-table) to configure the Clippy ruleset in the workspace's `Cargo.toml`. Each crate in the workspace now has the following in their own `Cargo.toml` to inherit the lints from the workspace: ```toml [lints] workspace = true ``` This allows for configuring rust-analyzer to show Clippy lints in the editor by using the following configuration in your Zed `settings.json`: ```json { "lsp": { "rust-analyzer": { "initialization_options": { "check": { "command": "clippy" } } } } ``` Release Notes: - N/A 2024-03-05 20:01:17 +03:00			`[lints]`
			`workspace = true`

chore: Extract `assets` module out of zed crate. (#3957) This essentially shaves off about 10% off of an incremental build after project change and potentially more if you're changing stuff like `welcome` that's very close to the `zed` crate in the dep graph. That's because macro expansion takes place even in incremental builds it seems? And zed (lib) + zed (bin) could take up to 4 seconds out of an incremental build, which is a lot in a 10s build. In reality though it shaves 1 second off of 5 seconds incremental 'welcome'/ 1s off of 10s 'project' builds. Note that we had `assets` crate in the past (removed in #2575 /cc @maxbrunsfeld), but this is a bit different, because `assets` is a dependency of just zed and nothing else. We essentially cache macro expansion results ourselves. Release Notes: - N/A 2024-01-09 00:49:14 +03:00			`[dependencies]`
Sort dependencies in `Cargo.toml` files (#7126) This PR sorts the dependency lists in our `Cargo.toml` files so that they are in alphabetical order. This should make them easier to visually scan when looking for a dependency. Apologies in advance for any merge conflicts 🙈 Release Notes: - N/A 2024-01-31 05:41:29 +03:00			`anyhow.workspace = true`
chore: Move workspace dependencies to workspace.dependencies (#7454) We should prefer referring to local deps via `.workspace = true` from now on. Release Notes: - N/A 2024-02-06 22:41:36 +03:00			`gpui.workspace = true`
chore: Extract `assets` module out of zed crate. (#3957) This essentially shaves off about 10% off of an incremental build after project change and potentially more if you're changing stuff like `welcome` that's very close to the `zed` crate in the dep graph. That's because macro expansion takes place even in incremental builds it seems? And zed (lib) + zed (bin) could take up to 4 seconds out of an incremental build, which is a lot in a 10s build. In reality though it shaves 1 second off of 5 seconds incremental 'welcome'/ 1s off of 10s 'project' builds. Note that we had `assets` crate in the past (removed in #2575 /cc @maxbrunsfeld), but this is a bit different, because `assets` is a dependency of just zed and nothing else. We essentially cache macro expansion results ourselves. Release Notes: - N/A 2024-01-09 00:49:14 +03:00			`rust-embed.workspace = true`