`protoc-gen-prost-serde` with external types? about protoc-gen-prost HOT 3 CLOSED

google-api-proto doesn't produce JSON bindings (serde::Serialize/serde::Deserialize impls) for the types in that crate. This means that the foreign messages/enums won't have the expected impls available to enable JSON serialization/deserialization if included as fields in messages from your local protobuf definitions.

Some options are:

• Generate the bindings for the Google API locally, rather than through the external crate. This would enable protoc-gen-prost-serde to generate the canonical JSON serializations for the whole API.
• Don't directly depend on these foreign types in your local crate, and instead do a mapping where appropriate. This is a bit less fun and requires some boilerplate, but also removes your direct dependency on the representation of the message in the Google APIs.
• Suggest a way to suppress the generation of serde::Serialize implementations on certain messages or files. This would need to be done in a way that pbjson would be able to support, as we largely delegate the generation of this process to their crate.

from protoc-gen-prost.

Thank you for your reply!
As a workaround, I've copied the proto files into my project. It's not great but unblocked me.

I think your comment is a great reference for folks who are stuck on the same issue, so I'll close the issue.

from protoc-gen-prost.

Out of curiosity, is having protoc-gen-prost generate code for external types such as google.rpc.Status not possible or not desirable? It would make the experience much smoother.

from protoc-gen-prost.