Today, we have two places where we have a .proto file and we generate protos out of it:
Each one with their own generator scripts.
After #577, we might have one more, so in order to avoid another copy-paste of the code generator logic, it'd be nice to have a single central place that we use for code generation.
My intuition tells me that having a single workspace decoupled folder called codegen/ in the root of the project with a structure similar to the other gen/ folders can work well. This codegen/ folder will be like it's own isolated Rust project detached from the main workspace (like the other gen/ folders) in charge of generating proto stubs for the whole project at once.
Today, we have two places where we have a .proto file and we generate protos out of it:
Each one with their own generator scripts.
After #577, we might have one more, so in order to avoid another copy-paste of the code generator logic, it'd be nice to have a single central place that we use for code generation.
My intuition tells me that having a single workspace decoupled folder called
codegen/in the root of the project with a structure similar to the othergen/folders can work well. Thiscodegen/folder will be like it's own isolated Rust project detached from the main workspace (like the other gen/ folders) in charge of generating proto stubs for the whole project at once.