ExprValue
extends Message
in package
The value of an evaluated expression.
Generated from protobuf message google.api.expr.v1beta1.ExprValue
Table of Contents
Properties
- $kind : mixed
Methods
- __construct() : mixed
- Constructor.
- getError() : ErrorSet|null
- The set of errors in the critical path of evalution.
- getKind() : string
- getUnknown() : UnknownSet|null
- The set of unknowns in the critical path of evaluation.
- getValue() : Value|null
- A concrete value.
- hasError() : mixed
- hasUnknown() : mixed
- hasValue() : mixed
- setError() : $this
- The set of errors in the critical path of evalution.
- setUnknown() : $this
- The set of unknowns in the critical path of evaluation.
- setValue() : $this
- A concrete value.
Properties
$kind
protected
mixed
$kind
Methods
__construct()
Constructor.
public
__construct([array<string|int, mixed> $data = NULL ]) : mixed
Parameters
- $data : array<string|int, mixed> = NULL
-
{ Optional. Data for populating the Message object.
@type \Google\Api\Expr\V1beta1\Value $value A concrete value. @type \Google\Api\Expr\V1beta1\ErrorSet $error 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. @type \Google\Api\Expr\V1beta1\UnknownSet $unknown 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>}
getError()
The set of errors in the critical path of evalution.
public
getError() : ErrorSet|null
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.
Generated from protobuf field .google.api.expr.v1beta1.ErrorSet error = 2 [json_name = "error"];
Return values
ErrorSet|nullgetKind()
public
getKind() : string
Return values
stringgetUnknown()
The set of unknowns in the critical path of evaluation.
public
getUnknown() : UnknownSet|null
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:
Generated from protobuf field .google.api.expr.v1beta1.UnknownSet unknown = 3 [json_name = "unknown"];
Return values
UnknownSet|nullgetValue()
A concrete value.
public
getValue() : Value|null
Generated from protobuf field .google.api.expr.v1beta1.Value value = 1 [json_name = "value"];
Return values
Value|nullhasError()
public
hasError() : mixed
hasUnknown()
public
hasUnknown() : mixed
hasValue()
public
hasValue() : mixed
setError()
The set of errors in the critical path of evalution.
public
setError(ErrorSet $var) : $this
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.
Generated from protobuf field .google.api.expr.v1beta1.ErrorSet error = 2 [json_name = "error"];
Parameters
- $var : ErrorSet
Return values
$thissetUnknown()
The set of unknowns in the critical path of evaluation.
public
setUnknown(UnknownSet $var) : $this
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:
Generated from protobuf field .google.api.expr.v1beta1.UnknownSet unknown = 3 [json_name = "unknown"];
Parameters
- $var : UnknownSet
Return values
$thissetValue()
A concrete value.
public
setValue(Value $var) : $this
Generated from protobuf field .google.api.expr.v1beta1.Value value = 1 [json_name = "value"];
Parameters
- $var : Value