jj/lib/gen-protos/Cargo.toml

[package]
name = "gen-protos"
description = "Generate Protocol Buffers definitions for the jj-lib crate"
publish = false

version = { workspace = true }
edition = { workspace = true }
license = { workspace = true }

[dependencies]
prost-build = { workspace = true }

[lints]
workspace = true
lib: replace protobuf crate with prost 2022-12-21 19:14:46 +00:00			`[package]`
			`name = "gen-protos"`
cargo: unify a lot of crate metadata in the workspace Summary: There's no need to go around specifying `rust-version` or `edition` or `version` several times, now that we have a global workspace. Instead, inherit workspace metadata from the top-level Cargo.toml file. Signed-off-by: Austin Seipp <aseipp@pobox.com> Change-Id: Iaf905445978ed2b3377239dcdb8a6c32 2023-08-05 22:14:11 +00:00			`description = "Generate Protocol Buffers definitions for the jj-lib crate"`
lib: replace protobuf crate with prost 2022-12-21 19:14:46 +00:00			`publish = false`

Use `{ workspace = true }` to appease VS Code's `Cargo.toml` parser The VS Code "Better TOML" plugin (which I think most of our VS Code developers use?) doesn't support the `x.y = z` syntax at the top level, even though it's valid TOML. This is also useful if we ever want to add additional properties in different sub-crates (although unlikely for the near future). 2023-08-22 16:41:42 +00:00			`version = { workspace = true }`
			`edition = { workspace = true }`
			`license = { workspace = true }`
cargo: unify a lot of crate metadata in the workspace Summary: There's no need to go around specifying `rust-version` or `edition` or `version` several times, now that we have a global workspace. Instead, inherit workspace metadata from the top-level Cargo.toml file. Signed-off-by: Austin Seipp <aseipp@pobox.com> Change-Id: Iaf905445978ed2b3377239dcdb8a6c32 2023-08-05 22:14:11 +00:00
lib: replace protobuf crate with prost 2022-12-21 19:14:46 +00:00			`[dependencies]`
Use `{ workspace = true }` to appease VS Code's `Cargo.toml` parser The VS Code "Better TOML" plugin (which I think most of our VS Code developers use?) doesn't support the `x.y = z` syntax at the top level, even though it's valid TOML. This is also useful if we ever want to add additional properties in different sub-crates (although unlikely for the near future). 2023-08-22 16:41:42 +00:00			`prost-build = { workspace = true }`
cargo: inherit lints configuration from workspace 2024-10-02 20:11:37 +00:00
			`[lints]`
			`workspace = true`