You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
An expression of the following form will type-check just fine, if the identifier x is declared as a type containing a struct type reference to a fully qualified protobuf message name:
Expected behavior
No runtimes across all CEL stacks can consume this AST to produce a new message, nor is it planned to do so. Type-checker should be made to explicitly fail in this scenario.
Additional context
java xref b/398261303
The issue is less pronounced in CEL-Go, since it requires an additional step of declaring the type variable fetched from a type provider, but the issue is still present nonetheless.
The text was updated successfully, but these errors were encountered:
l46kok
changed the title
Prevent type-checking of a message create expression with a type identifier
Prevent type-checking of a message create expression with a type variable
Feb 21, 2025
Describe the bug
An expression of the following form will type-check just fine, if the identifier
x
is declared as a type containing a struct type reference to a fully qualified protobuf message name:To Reproduce
Check which components this affects:
Expected behavior
No runtimes across all CEL stacks can consume this AST to produce a new message, nor is it planned to do so. Type-checker should be made to explicitly fail in this scenario.
Additional context
java xref b/398261303
The issue is less pronounced in CEL-Go, since it requires an additional step of declaring the type variable fetched from a type provider, but the issue is still present nonetheless.
The text was updated successfully, but these errors were encountered: