forked from google/cel-spec
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Sync CEL proto changes to cel spec. (google#16)
* Sync CEL proto changes to cel spec. * Sync CEL proto changes to cel spec. * Sync CEL proto changes to cel spec. * Sycn CEL proto changes to cel spec.
- Loading branch information
Showing
9 changed files
with
459 additions
and
527 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,100 @@ | ||
| syntax = "proto3"; | ||
|
|
||
| package google.api.expr.v1; | ||
|
|
||
| option cc_enable_arenas = true; | ||
| option java_multiple_files = true; | ||
| option java_outer_classname = "EvalProto"; | ||
| option java_package = "com.google.api.expr.v1"; | ||
|
|
||
| import "proto/v1/value.proto"; | ||
| import "google/rpc/status.proto"; | ||
|
|
||
| // The state of an evaluation. | ||
| // | ||
| // Can represent an inital, partial, or completed state of evaluation. | ||
| message EvalState { | ||
| // The unique values referenced in this message. | ||
| repeated ExprValue values = 1; | ||
|
|
||
| // A single evalution result. | ||
| message Result { | ||
| // The id of the expression this result if for. | ||
| int64 expr = 1; | ||
| // The index in `values` of the resulting value. | ||
| int64 value = 2; | ||
| } | ||
|
|
||
| // An ordered list of results. | ||
| // | ||
| // Tracks the flow of evaluation through the expression. | ||
| // May be sparse. | ||
| repeated Result results = 3; | ||
| } | ||
|
|
||
| // The value of an evaluated expression. | ||
| message ExprValue { | ||
| // An expression can resolve to a value, error or unknown. | ||
| oneof kind { | ||
| Value value = 1; | ||
|
|
||
| // The set of errors in the critical path of evalution. | ||
| // | ||
| // Only errors in the critical path are included. For example, | ||
| // `(<error1> || true) && <error2>` will only result in `<error2>`, | ||
| // while `<error1> || <error2>` will result in both `<error1>` and | ||
| // `<error2>`. | ||
| // | ||
| // Errors cause by the presence of other errors are not included in the | ||
| // set. For example `<error1>.foo`, `foo(<error1>)`, and `<error1> + 1` will | ||
| // only result in `<error1>`. | ||
| // | ||
| // Multiple errors *might* be included when evaluation could result | ||
| // in different errors. For example `<error1> + <error2>` and | ||
| // `foo(<error1>, <error2>)` may result in `<error1>`, `<error2>` or both. | ||
| // The exact subset of errors included for this case is unspecified and | ||
| // depends on the implementation details of the evaluator. | ||
| ErrorSet error = 2; | ||
|
|
||
| // The set of unknowns in the critical path of evaluation. | ||
| // | ||
| // Unknown behaves identically to Error with regards to propagation. | ||
| // Specifically, only unknowns in the critical path are included, unknowns | ||
| // caused by the presence of other unknowns are not included, and multiple | ||
| // unknowns *might* be included included when evaluation could result in | ||
| // different unknowns. For example: | ||
| // | ||
| // (<unknown[1]> || true) && <unknown[2]> -> <unknown[2]> | ||
| // <unknown[1]> || <unknown[2]> -> <unknown[1,2]> | ||
| // <unknown[1]>.foo -> <unknown[1]> | ||
| // foo(<unknown[1]>) -> <unknown[1]> | ||
| // <unknown[1]> + <unknown[2]> -> <unknown[1]> or <unknown[2[> | ||
| // | ||
| // Unknown takes precidence over Error in cases where a `Value` can short | ||
| // circuit the result: | ||
| // | ||
| // <error> || <unknown> -> <unknown> | ||
| // <error> && <unknown> -> <unknown> | ||
| // | ||
| // Errors take precidence in all other cases: | ||
| // | ||
| // <unknown> + <error> -> <error> | ||
| // foo(<unknown>, <error>) -> <error> | ||
| UnknownSet unknown = 3; | ||
| }; | ||
| } | ||
|
|
||
| // A set of errors. | ||
| // | ||
| // The errors included depend on the context. See `ExprValue.error`. | ||
| message ErrorSet { | ||
| repeated google.rpc.Status errors = 1; | ||
| } | ||
|
|
||
| // A set of expressions for which the value is unknown. | ||
| // | ||
| // The unknowns included depend on the context. See `ExprValue.unknown`. | ||
| message UnknownSet { | ||
| // The ids of the expressions with unknown values. | ||
| repeated int64 exprs = 1; | ||
| } |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.