@@ -16,8 +16,8 @@ syntax = "proto3";
16
16
17
17
package cel.expr ;
18
18
19
+ import "google/protobuf/any.proto" ;
19
20
import "cel/expr/value.proto" ;
20
- import "google/rpc/status.proto" ;
21
21
22
22
option cc_enable_arenas = true ;
23
23
option go_package = "cel.dev/expr" ;
@@ -104,9 +104,31 @@ message ExprValue {
104
104
//
105
105
// The errors included depend on the context. See `ExprValue.error`.
106
106
message ErrorSet {
107
- repeated google.rpc.Status errors = 1 ;
107
+ // Errors that could come up during evaluation phase.
108
+ repeated Status errors = 1 ;
108
109
}
109
110
111
+ // Each `Status` message contains three pieces of data: error code, error message,
112
+ // and error details.
113
+ //
114
+ // You can find out more about this error model and how to work with it in the
115
+ // [API Design Guide](https://cloud.google.com/apis/design/errors).
116
+ //
117
+ // Status value is intended to be wire and field compatible with `google.rpc.Status`.
118
+ message Status {
119
+ // The status code, which should be an enum value of [google.rpc.Code][].
120
+ int32 code = 1 ;
121
+
122
+ // A developer-facing error message, which should be in English. Any
123
+ // user-facing error message should be localized and sent in the
124
+ // [Status.details][] field, or localized by the client.
125
+ string message = 2 ;
126
+
127
+ // A list of messages that carry the error details. There is a common set of
128
+ // message types for APIs to use.
129
+ repeated google.protobuf.Any details = 3 ;
130
+ }
131
+
110
132
// A set of expressions for which the value is unknown.
111
133
//
112
134
// The unknowns included depend on the context. See `ExprValue.unknown`.
0 commit comments