It's unfortunate that the spec doesn't contain custom fields to a sub-object like other RPC specs, like proto Status [1]. They should have had the message go in

It's unfortunate that the spec doesn't contain custom fields to a sub-object like other RPC specs, like proto Status [1]. They should have had the message go into a field named "message" and not "detail". And have a field like "details" where the opaque type is serialized, which should be named by the "type" field. The problem is that systems with existing error types may have field name conflicts with type, title, status, detail, or instance, so we'd just dump the actual error into a custom "extension member" which by definition, isn't standard. [1] https://github.com/googleapis/googleapis/blob/1c8a25ab153eef5757227170853dc80c9f92c21c/google/rpc/status.proto#L35 https://github.com/googleapis/googleapis/blob/1c8a25ab153eef...