langfingaz/anki
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
de8f62f831
anki/rslib/proto/Cargo.toml

26 lines
585 B
TOML
Raw Normal View History

Move protobuf generation into a separate crate; write .py interface in Rust A couple of motivations for this: - genbackend.py was somewhat messy, and difficult to change with the lack of types. The mobile clients used it as a base for their generation, so improving it will make life easier for them too, once they're ported. - It will make it easier to write a .ts generator in the future - We currently implement a bunch of helper methods on protobuf types which don't allow us to compile the protobuf types until we compile the Anki crate. If we change this in the future, we will be able to do more of the compilation up-front. We no longer need to record the services in the proto file, as we can extract the service order from the compiled protos. Support for map types has also been added.
2023-06-11 14:17:41 +02:00
[package]
name = "anki_proto"
publish = false
description = "Anki's Rust library protobuf code"
version.workspace = true
authors.workspace = true
edition.workspace = true
license.workspace = true
rust-version.workspace = true
[build-dependencies]
Split io.rs into separate crate, and use it in proto build Will be handy to use it in our other scripts in the future too - thanks Rumo! Results of benchmarking ./run before and after these crate splits: - Touching a proto file leads to a slight increase: about +90ms - Touching an rslib file leads to a bigger decrease, as there's less to recompile: about -700ms And ./ninja test is even better: about +200ms and -3800ms.
2023-06-12 07:24:57 +02:00
anki_io = { version = "0.0.0", path = "../io" }
Move protobuf generation into a separate crate; write .py interface in Rust A couple of motivations for this: - genbackend.py was somewhat messy, and difficult to change with the lack of types. The mobile clients used it as a base for their generation, so improving it will make life easier for them too, once they're ported. - It will make it easier to write a .ts generator in the future - We currently implement a bunch of helper methods on protobuf types which don't allow us to compile the protobuf types until we compile the Anki crate. If we change this in the future, we will be able to do more of the compilation up-front. We no longer need to record the services in the proto file, as we can extract the service order from the compiled protos. Support for map types has also been added.
2023-06-11 14:17:41 +02:00
anyhow = "1.0.71"
inflections = "1.1.1"
prost-build = "0.11.9"
prost-reflect = "0.11.4"
prost-types = "0.11.9"
Move generated protobuf into anki_proto Due to the orphan rule, this meant removing our usages of impl ProtoStruct, or converting them to a trait when they were used commonly. rslib now directly references anki_proto and anki_i18n, instead of 'pub use'-ing them, and we can put the generated files back in OUT_DIR.
2023-06-12 03:40:10 +02:00
[dependencies]
num_enum = "0.6.1"
prost = "0.11.9"
serde = { version = "1.0.164", features = ["derive"] }
snafu = "0.7.4"
strum = { version = "0.24.1", features = ["derive"] }
Reference in New Issue Copy Permalink