Request message fields that are used as path parameters in gRPC Transcoding annotations currently have implicit presence (i.e., since they use proto3 syntax, they don't have the optional modifier applied to them) because gRPC-Gateway code generation will fail (see grpc-ecosystem/grpc-gateway#6352) if an optional field is used in a path parameter.
This behavior in gRPC-Gateway has been reverted in grpc-ecosystem/grpc-gateway#6416. Once it is included in a release (most likely any release after 2.28.0), we should change all of our fields to use explicit presence because doing so is recommended by protobuf for maximum compatibility with protobuf editions.
Request message fields that are used as path parameters in gRPC Transcoding annotations currently have implicit presence (i.e., since they use
proto3syntax, they don't have theoptionalmodifier applied to them) because gRPC-Gateway code generation will fail (see grpc-ecosystem/grpc-gateway#6352) if an optional field is used in a path parameter.This behavior in gRPC-Gateway has been reverted in grpc-ecosystem/grpc-gateway#6416. Once it is included in a release (most likely any release after 2.28.0), we should change all of our fields to use explicit presence because doing so is recommended by protobuf for maximum compatibility with protobuf editions.