-
Notifications
You must be signed in to change notification settings - Fork 302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
proto: align proto packages to rust crates #3077
Conversation
A follow-on step once this PR lands (which we should do as soon as the Rust code compiles again) is to split up the RPC definitions in the |
VSCode Search&Replace core::crypto::v1alpha1 to penumbra::crypto::tct::v1alpha1 files to include crates/crypto/tct
85a0adb
to
b961f72
Compare
It was easier than I expected to patch up the import paths; we'll still need to go through and fix up the |
It looks like |
Refs #2288 |
After reorganizing the Rust crates into a coherent heirarchy, we never did the same for the .proto files. This PR does that.
Currently, this just reorganizes the proto files, updates the
proto-compiler
tool, and regenerates the source code. What's remaining is to update all of the import paths in all of the domain type implementations that reference the proto structures. I'd suggest we swarm that part tomorrow morning, using live share + search&replace, since this PR will conflict with everything else (and break all of the protos used by other tooling like the web interfaces).I don't think we should try to update all of the
TYPE_URL
s at this point; those are used for genericAny
support, which we don't usually make use of, and landing the changes ASAP is more important than restoring that functionality (except where we know we need it because eg the smoke test fails).