gitbutler/crates/gitbutler-sync/Cargo.toml

[package]
name = "gitbutler-sync"
version = "0.0.0"
edition = "2021"
authors = ["GitButler <gitbutler@gitbutler.com>"]
publish = false

[dependencies]
anyhow = "1.0.86"
tracing = "0.1.40"
itertools = "0.13"
git2.workspace = true
gitbutler-core.workspace = true
gitbutler-oplog.workspace = true
gitbutler-branchstate.workspace = true
gitbutler-command-context.workspace = true
gitbutler-project.workspace = true
gitbutler-user.workspace = true
gitbutler-branch.workspace = true
move cloud sync functionality to its own crate 2024-07-07 20:22:41 +03:00			`[package]`
			`name = "gitbutler-sync"`
			`version = "0.0.0"`
			`edition = "2021"`
			`authors = ["GitButler <gitbutler@gitbutler.com>"]`
			`publish = false`

			`[dependencies]`
			`anyhow = "1.0.86"`
			`tracing = "0.1.40"`
			`itertools = "0.13"`
			`git2.workspace = true`
			`gitbutler-core.workspace = true`
move oplog to its own crate This protects us from cyclic dependencies. Unfortunatelly as part of this, i had to introduce the imp Project as trait implementations since now Project is foreign 2024-07-07 21:00:01 +03:00			`gitbutler-oplog.workspace = true`
move branch state into a separate crate 2024-07-07 22:26:07 +03:00			`gitbutler-branchstate.workspace = true`
move ProjectRepo into its own crate This type currently acts more or less like a command context that lives for the duration of the request. Regardless of if we wanna keep this pattern or not, separating it out helps us split up core 2024-07-08 14:23:03 +03:00			`gitbutler-command-context.workspace = true`
move project module in a separate gitbutler-project crate 2024-07-08 16:33:26 +03:00			`gitbutler-project.workspace = true`
extract user as its own crate out of core 2024-07-08 19:58:29 +03:00			`gitbutler-user.workspace = true`
move target module to gitbutler-branch crate 2024-07-09 01:40:10 +03:00			`gitbutler-branch.workspace = true`