...

Source file src/github.com/grpc-ecosystem/grpc-gateway/v2/examples/internal/clients/responsebody/model_rpc_status.go

Documentation: github.com/grpc-ecosystem/grpc-gateway/v2/examples/internal/clients/responsebody

     1  /*
     2   * examples/internal/proto/examplepb/response_body_service.proto
     3   *
     4   * No description provided (generated by Swagger Codegen https://github.com/swagger-api/swagger-codegen)
     5   *
     6   * API version: version not set
     7   * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
     8   */
     9  
    10  package responsebody
    11  
    12  // The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details.  You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors).
    13  type RpcStatus struct {
    14  	// The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
    15  	Code int32 `json:"code,omitempty"`
    16  	// A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
    17  	Message string `json:"message,omitempty"`
    18  	// A list of messages that carry the error details.  There is a common set of message types for APIs to use.
    19  	Details []ProtobufAny `json:"details,omitempty"`
    20  }
    21  

View as plain text