-
Notifications
You must be signed in to change notification settings - Fork 29
Update protovalidate #293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update protovalidate #293
Conversation
Signed-off-by: Sri Krishna <[email protected]>
|
The latest Buf updates on your PR. Results from workflow Buf / validate-protos (pull_request).
|
Signed-off-by: Sri Krishna <[email protected]>
Signed-off-by: Sri Krishna <[email protected]>
Signed-off-by: Sri Krishna <[email protected]>
Signed-off-by: Sri Krishna <[email protected]>
Signed-off-by: Sri Krishna <[email protected]>
Signed-off-by: Sri Krishna <[email protected]>
| out[i].Env, err = out[i].Env.Extend( | ||
| cel.Constant( | ||
| "rule", | ||
| pvcel.ProtoFieldToType(ruleDescriptor, true, false), | ||
| pvcel.ProtoFieldToValue(ruleDescriptor, ruleValue, false), | ||
| ), | ||
| ) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This never worked for message fields. The ProtoFieldToValue is using the default adapter of cel-go that doesn't handle protobuf messages except for wrappers. This always returned an error value.
Because we try to reduce the AST ahead of time and the rule variable was always being optimized away, we never hit a problem.
Signed-off-by: Sri Krishna <[email protected]>
No description provided.