OneOf Handling about cel-go HOT 2 CLOSED

@jacobmikesell this is a limitation of context protos in that the top level fields are all treated as variables, even within oneof values, so it's practically impossible to tell which one is set and still ensure that all possible variables are defined at runtime. Not publishing a variable in this case would be a runtime error rather than a boolean result.

This is working as intended, and working like field accesses work for oneofs outside the context case. The only difference is you can't test which oneof case was set.

I realize it's a bit confusing, but the feature is really intended to be a simplification for some users who manage a lot of variables in a common location outside CEL.

from cel-go.

@TristonianJones Thanks for the quick response!

from cel-go.