zed-industries/zed
1
1
Fork 0
mirror of https://github.com/zed-industries/zed.git synced 2024-11-08 07:35:01 +03:00
Code Issues Packages Projects Releases Wiki Activity
fa19bc98ac
zed/crates/client/Cargo.toml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

71 lines
1.9 KiB
TOML
Raw Normal View History

Extract worktree, rpc_client, and util crates Co-Authored-By: Max Brunsfeld <maxbrunsfeld@gmail.com>
2021-10-04 22:07:35 +03:00
[package]
Rename rpc_client -> client Co-Authored-By: Nathan Sobo <nathan@zed.dev>
2021-10-05 03:14:21 +03:00
name = "client"
Extract worktree, rpc_client, and util crates Co-Authored-By: Max Brunsfeld <maxbrunsfeld@gmail.com>
2021-10-04 22:07:35 +03:00
version = "0.1.0"
Use Rust 2021 edition in all crates Co-Authored-By: Nathan Sobo <nathan@zed.dev>
2022-01-26 23:50:31 +03:00
edition = "2021"
Added complete scripts for generating third party license files
2023-01-18 23:28:02 +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
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
Name the root file of every crate after the crate to ease navigation Co-Authored-By: Max Brunsfeld <maxbrunsfeld@gmail.com>
2021-11-30 22:46:39 +03:00
[lib]
path = "src/client.rs"
Disable doctests for all libraries We don't use them, and they add a lot of noise to the test output when running all tests in the workspace.
2022-03-04 03:15:56 +03:00
doctest = false
Name the root file of every crate after the crate to ease navigation Co-Authored-By: Max Brunsfeld <maxbrunsfeld@gmail.com>
2021-11-30 22:46:39 +03:00
Extract worktree, rpc_client, and util crates Co-Authored-By: Max Brunsfeld <maxbrunsfeld@gmail.com>
2021-10-04 22:07:35 +03:00
[features]
Add `SystemClock` (#8239) This PR adds a `SystemClock` trait for abstracting away the system clock. This allows us to swap out the real system clock with a `FakeSystemClock` in the tests, thus allowing the fake passage of time. We're using this in `Telemetry` to better mock the clock for testing purposes. Release Notes: - N/A
2024-02-23 06:28:08 +03:00
test-support = ["clock/test-support", "collections/test-support", "gpui/test-support", "rpc/test-support"]
Extract worktree, rpc_client, and util crates Co-Authored-By: Max Brunsfeld <maxbrunsfeld@gmail.com>
2021-10-04 22:07:35 +03:00
[dependencies]
Add development credentials provider (#11505) This PR adds a new development credentials provider for the purpose of streamlining local development against production collab. ## Problem Today if you want to run a development build of Zed against the production collab server, you need to either: 1. Enter your keychain password every time in order to retrieve your saved credentials 2. Re-authenticate with zed.dev every time - This can get annoying as you need to pop out into a browser window - I've also seen cases where if you re-auth too many times in a row GitHub will make you confirm the authentication, as it looks suspicious ## Solution This PR decouples the concept of the credentials provider from the keychain, and adds a new development credentials provider to address this specific case. Now when running a development build of Zed and the `ZED_DEVELOPMENT_AUTH` environment variable is set to a non-empty value, the credentials will be saved to disk instead of the system keychain. While this is not as secure as storing them in the system keychain, since it is only used for development the tradeoff seems acceptable for the resulting improvement in UX. Release Notes: - N/A
2024-05-07 20:59:18 +03:00
anyhow.workspace = true
async-recursion = "0.3"
Update http crate name (#15041) Release Notes: - N/A
2024-07-24 01:01:05 +03:00
async-tungstenite = { workspace = true, features = ["async-std", "async-native-tls"] }
Hoist `chrono` dependency to workspace level (#8414) This PR hoists the `chrono` dependency to the workspace level. Release Notes: - N/A
2024-02-26 02:52:59 +03:00
chrono = { workspace = true, features = ["serde"] }
Add `SystemClock` (#8239) This PR adds a `SystemClock` trait for abstracting away the system clock. This allows us to swap out the real system clock with a `FakeSystemClock` in the tests, thus allowing the fake passage of time. We're using this in `Telemetry` to better mock the clock for testing purposes. Release Notes: - N/A
2024-02-23 06:28:08 +03:00
clock.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
collections.workspace = true
feature_flags.workspace = true
Pull app / OS info out of GPUI, add Linux information, make fallible window initialization (#12869) TODO: - [x] Finish GPUI changes on other operating systems This is a largely internal change to how we report data to our diagnostics and telemetry. This PR also includes an update to our blade backend which allows us to report errors in a more useful way when failing to initialize blade. Release Notes: - N/A --------- Co-authored-by: Conrad Irwin <conrad.irwin@gmail.com>
2024-06-11 21:43:12 +03:00
fs.workspace = true
:art: Specify more dependencies at the workspace level
2023-04-25 03:41:55 +03:00
futures.workspace = true
Add development credentials provider (#11505) This PR adds a new development credentials provider for the purpose of streamlining local development against production collab. ## Problem Today if you want to run a development build of Zed against the production collab server, you need to either: 1. Enter your keychain password every time in order to retrieve your saved credentials 2. Re-authenticate with zed.dev every time - This can get annoying as you need to pop out into a browser window - I've also seen cases where if you re-auth too many times in a row GitHub will make you confirm the authentication, as it looks suspicious ## Solution This PR decouples the concept of the credentials provider from the keychain, and adds a new development credentials provider to address this specific case. Now when running a development build of Zed and the `ZED_DEVELOPMENT_AUTH` environment variable is set to a non-empty value, the credentials will be saved to disk instead of the system keychain. While this is not as secure as storing them in the system keychain, since it is only used for development the tradeoff seems acceptable for the resulting improvement in UX. Release Notes: - N/A
2024-05-07 20:59:18 +03:00
gpui.workspace = true
Update http crate name (#15041) Release Notes: - N/A
2024-07-24 01:01:05 +03:00
http_client.workspace = true
:art: Specify more dependencies at the workspace level
2023-04-25 03:41:55 +03:00
lazy_static.workspace = true
log.workspace = true
linux cli (#11585) - [x] Build out cli on linux - [x] Add support for --dev-server-token sent by the CLI - [x] Package cli into the .tar.gz - [x] Link the cli to ~/.local/bin in install.sh Release Notes: - linux: Add cli support for managing zed
2024-05-10 06:08:49 +03:00
once_cell.workspace = true
Extract paths out of `util` (#13182) This PR extracts the definition of the various Zed paths out of `util` and into a new `paths` crate. `util` is for generic utils, while these paths are Zed-specific. For instance, `gpui` depends on `util`, and it shouldn't have knowledge of these paths, since they are only used by Zed. Release Notes: - N/A
2024-06-18 02:27:42 +03:00
paths.workspace = true
:art: Specify more dependencies at the workspace level
2023-04-25 03:41:55 +03:00
parking_lot.workspace = true
postage.workspace = true
rand.workspace = true
Add development credentials provider (#11505) This PR adds a new development credentials provider for the purpose of streamlining local development against production collab. ## Problem Today if you want to run a development build of Zed against the production collab server, you need to either: 1. Enter your keychain password every time in order to retrieve your saved credentials 2. Re-authenticate with zed.dev every time - This can get annoying as you need to pop out into a browser window - I've also seen cases where if you re-auth too many times in a row GitHub will make you confirm the authentication, as it looks suspicious ## Solution This PR decouples the concept of the credentials provider from the keychain, and adds a new development credentials provider to address this specific case. Now when running a development build of Zed and the `ZED_DEVELOPMENT_AUTH` environment variable is set to a non-empty value, the credentials will be saved to disk instead of the system keychain. While this is not as secure as storing them in the system keychain, since it is only used for development the tradeoff seems acceptable for the resulting improvement in UX. Release Notes: - N/A
2024-05-07 20:59:18 +03:00
release_channel.workspace = true
rpc.workspace = true
Define telemetry settings in the client crate
2023-05-10 22:17:52 +03:00
schemars.workspace = true
Add memory and cpu events Co-Authored-By: Julia <30666851+ForLoveOfCats@users.noreply.github.com>
2023-10-03 02:35:31 +03:00
serde.workspace = true
gpui: Further docs refinement & moved some reexports into 'private' module (#3935) This commit mostly fixes invalid URLs in docstrings. It also encapsulates crates we reexport (serde stuff + linkme) into a public module named "private" in order to reduce the API surfaced through docs. Moreover, I fixed up a bunch of crates that were pulling serde_json in through gpui explicitly instead of using Cargo manifest. Release Notes: - N/A
2024-01-07 16:14:21 +03:00
serde_json.workspace = true
Add development credentials provider (#11505) This PR adds a new development credentials provider for the purpose of streamlining local development against production collab. ## Problem Today if you want to run a development build of Zed against the production collab server, you need to either: 1. Enter your keychain password every time in order to retrieve your saved credentials 2. Re-authenticate with zed.dev every time - This can get annoying as you need to pop out into a browser window - I've also seen cases where if you re-auth too many times in a row GitHub will make you confirm the authentication, as it looks suspicious ## Solution This PR decouples the concept of the credentials provider from the keychain, and adds a new development credentials provider to address this specific case. Now when running a development build of Zed and the `ZED_DEVELOPMENT_AUTH` environment variable is set to a non-empty value, the credentials will be saved to disk instead of the system keychain. While this is not as secure as storing them in the system keychain, since it is only used for development the tradeoff seems acceptable for the resulting improvement in UX. Release Notes: - N/A
2024-05-07 20:59:18 +03:00
settings.workspace = true
Add telemetry events backend for collab (#8220) Send telemetry to collab not zed.dev Release Notes: - N/A --------- Co-authored-by: Marshall <marshall@zed.dev> Co-authored-by: Marshall Bowers <elliott.codes@gmail.com>
2024-02-23 19:13:28 +03:00
sha2.workspace = true
:art: Specify more dependencies at the workspace level
2023-04-25 03:41:55 +03:00
smol.workspace = true
Add memory and cpu events Co-Authored-By: Julia <30666851+ForLoveOfCats@users.noreply.github.com>
2023-10-03 02:35:31 +03:00
sysinfo.workspace = true
Add telemetry events backend for collab (#8220) Send telemetry to collab not zed.dev Release Notes: - N/A --------- Co-authored-by: Marshall <marshall@zed.dev> Co-authored-by: Marshall Bowers <elliott.codes@gmail.com>
2024-02-23 19:13:28 +03:00
telemetry_events.workspace = true
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
tempfile.workspace = true
Add development credentials provider (#11505) This PR adds a new development credentials provider for the purpose of streamlining local development against production collab. ## Problem Today if you want to run a development build of Zed against the production collab server, you need to either: 1. Enter your keychain password every time in order to retrieve your saved credentials 2. Re-authenticate with zed.dev every time - This can get annoying as you need to pop out into a browser window - I've also seen cases where if you re-auth too many times in a row GitHub will make you confirm the authentication, as it looks suspicious ## Solution This PR decouples the concept of the credentials provider from the keychain, and adds a new development credentials provider to address this specific case. Now when running a development build of Zed and the `ZED_DEVELOPMENT_AUTH` environment variable is set to a non-empty value, the credentials will be saved to disk instead of the system keychain. While this is not as secure as storing them in the system keychain, since it is only used for development the tradeoff seems acceptable for the resulting improvement in UX. Release Notes: - N/A
2024-05-07 20:59:18 +03:00
text.workspace = true
:art: Specify more dependencies at the workspace level
2023-04-25 03:41:55 +03:00
thiserror.workspace = true
time.workspace = true
Extract worktree, rpc_client, and util crates Co-Authored-By: Max Brunsfeld <maxbrunsfeld@gmail.com>
2021-10-04 22:07:35 +03:00
tiny_http = "0.8"
Add ability to copy a permalink to a line (#7119) This PR adds the ability to copy the permalink to a line from within Zed. This functionality is available through the `editor: copy permalink to line` action in the command palette: <img width="589" alt="Screenshot 2024-01-30 at 7 07 46 PM" src="https://github.com/zed-industries/zed/assets/1486634/332282cb-211f-4f16-9eb1-415bcfee9b7b"> Executing this action will create a permalink to the currently selected line(s) and copy it to the clipboard. Here is an example line: ``` https://github.com/maxdeviant/auk/blob/56c80e80112744740be1969c89fdd34db4be6f64/src/lib.rs#L25 ``` Currently, both GitHub and GitLab are supported. ### Notes and known limitations - In order to determine where to permalink to, we read the URL of the `origin` remote in Git. This feature will not work if the `origin` remote is not present. - Attempting to permalink to a ref that is not pushed to the origin will result in the link 404ing. - Attempting to permalink when Git is in a dirty state may not generate the right link. - For instance, modifying a file (e.g., adding new lines) and grabbing a permalink to it will result in incorrect line numbers. Release Notes: - Added the ability to copy a permalink to a line ([#6777](https://github.com/zed-industries/zed/issues/6777)). - Available via the `editor: copy permalink to line` action in the command palette.
2024-01-31 03:20:15 +03:00
url.workspace = true
Add development credentials provider (#11505) This PR adds a new development credentials provider for the purpose of streamlining local development against production collab. ## Problem Today if you want to run a development build of Zed against the production collab server, you need to either: 1. Enter your keychain password every time in order to retrieve your saved credentials 2. Re-authenticate with zed.dev every time - This can get annoying as you need to pop out into a browser window - I've also seen cases where if you re-auth too many times in a row GitHub will make you confirm the authentication, as it looks suspicious ## Solution This PR decouples the concept of the credentials provider from the keychain, and adds a new development credentials provider to address this specific case. Now when running a development build of Zed and the `ZED_DEVELOPMENT_AUTH` environment variable is set to a non-empty value, the credentials will be saved to disk instead of the system keychain. While this is not as secure as storing them in the system keychain, since it is only used for development the tradeoff seems acceptable for the resulting improvement in UX. Release Notes: - N/A
2024-05-07 20:59:18 +03:00
util.workspace = true
Move project event logic to telemetry.rs (#13166) I previously put this logic directly into `project.rs`, but it doesn't feel good to pollute that code with telemetry logic, so I've moved it over to `telemetry.rs`. Release Notes: - N/A
2024-06-17 22:52:59 +03:00
worktree.workspace = true
Fix dev dependencies in client/Cargo.toml
2022-01-10 18:03:55 +03:00
[dev-dependencies]
Add `SystemClock` (#8239) This PR adds a `SystemClock` trait for abstracting away the system clock. This allows us to swap out the real system clock with a `FakeSystemClock` in the tests, thus allowing the fake passage of time. We're using this in `Telemetry` to better mock the clock for testing purposes. Release Notes: - N/A
2024-02-23 06:28:08 +03:00
clock = { workspace = true, features = ["test-support"] }
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
collections = { workspace = true, features = ["test-support"] }
gpui = { workspace = true, features = ["test-support"] }
rpc = { workspace = true, features = ["test-support"] }
settings = { workspace = true, features = ["test-support"] }
util = { workspace = true, features = ["test-support"] }
Update http crate name (#15041) Release Notes: - N/A
2024-07-24 01:01:05 +03:00
http_client = { workspace = true, features = ["test-support"] }
Bundle linux deps (#11681) Inlcude linux deps in the bundle Release Notes: - N/A
2024-05-13 23:10:03 +03:00
Pull app / OS info out of GPUI, add Linux information, make fallible window initialization (#12869) TODO: - [x] Finish GPUI changes on other operating systems This is a largely internal change to how we report data to our diagnostics and telemetry. This PR also includes an update to our blade backend which allows us to report errors in a more useful way when failing to initialize blade. Release Notes: - N/A --------- Co-authored-by: Conrad Irwin <conrad.irwin@gmail.com>
2024-06-11 21:43:12 +03:00
[target.'cfg(target_os = "windows")'.dependencies]
windows.workspace = true
[target.'cfg(target_os = "macos")'.dependencies]
cocoa.workspace = true
Dynamicer builds (#13074) Fixes https://github.com/zed-industries/zed/issues/13073 Note that, contrary to the issue's text, we're still shipping a statically bundled sqlite3 after this PR. We use enough new features of sqlite, like `sqlite3_error_offset` and `STRICT`, that our minimum version (v3.38.0) is higher than is presumably accessible on Ubuntu. Release Notes: - N/A --------- Co-authored-by: Mikayla <mikayla@zed.dev>
2024-06-22 02:32:32 +03:00
async-native-tls = { version = "0.5.0", features = ["vendored"] }
Reference in New Issue Copy Permalink