-
Notifications
You must be signed in to change notification settings - Fork 135
/
error.go
46 lines (43 loc) · 2.47 KB
/
error.go
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
// Copyright 2024 Coinbase, Inc.
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
// Generated by: OpenAPI Generator (https://openapi-generator.tech)
package types
// Error Instead of utilizing HTTP status codes to describe node errors (which often do not have a
// good analog), rich errors are returned using this object. Both the code and message fields can be
// individually used to correctly identify an error. Implementations MUST use unique values for both
// fields.
type Error struct {
// Code is a network-specific error code. If desired, this code can be equivalent to an HTTP
// status code.
Code int32 `json:"code"`
// Message is a network-specific error message. The message MUST NOT change for a given code. In
// particular, this means that any contextual information should be included in the details
// field.
Message string `json:"message"`
// Description allows the implementer to optionally provide additional information about an
// error. In many cases, the content of this field will be a copy-and-paste from existing
// developer documentation. Description can ONLY be populated with generic information about a
// particular type of error. It MUST NOT be populated with information about a particular
// instantiation of an error (use `details` for this). Whereas the content of Error.Message
// should stay stable across releases, the content of Error.Description will likely change
// across releases (as implementers improve error documentation). For this reason, the content
// in this field is not part of any type assertion (unlike Error.Message).
Description *string `json:"description,omitempty"`
// An error is retriable if the same request may succeed if submitted again.
Retriable bool `json:"retriable"`
// Often times it is useful to return context specific to the request that caused the error
// (i.e. a sample of the stack trace or impacted account) in addition to the standard error
// message.
Details map[string]interface{} `json:"details,omitempty"`
}