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
Change
Currently, there is no option to remove built-in CEL functions when using cel.NewEnv. Also, there is no option to include standard built-in CEL functions when using cel.NewCustomEnv. The proposed change is to add an option to cel.NewEnv for excluding built-in functions or an option to cel.NewCustomEnv for including standard CEL functions.
The text was updated successfully, but these errors were encountered:
I'd really like the ability to set *decls.Functions on an Env directly. We used to be able to achieve setting stdlib functions (or a subset) by configuring functions.StandardOverloads() then passing these overloads into the Env directly.
@tonyhb@sapirpol this is a good feature request. I just haven't have time to work on it. I'm more in favor of preserving the functional options, but making it very easy to subset by type and function name.
Feature request checklist
Change
Currently, there is no option to remove built-in CEL functions when using
cel.NewEnv
. Also, there is no option to include standard built-in CEL functions when usingcel.NewCustomEnv
. The proposed change is to add an option tocel.NewEnv
for excluding built-in functions or an option tocel.NewCustomEnv
for including standard CEL functions.The text was updated successfully, but these errors were encountered: