Skip to content
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

Option to Remove Built-in CEL Functions #844

Open
2 of 3 tasks
sapirpol opened this issue Oct 11, 2023 · 2 comments
Open
2 of 3 tasks

Option to Remove Built-in CEL Functions #844

sapirpol opened this issue Oct 11, 2023 · 2 comments

Comments

@sapirpol
Copy link

Feature request checklist

  • There are no issues that match the desired change
  • The change is large enough it can't be addressed with a simple Pull Request
  • If this is a bug, please file a Bug Report.

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.

@tonyhb
Copy link

tonyhb commented Dec 2, 2023

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.

@TristonianJones
Copy link
Collaborator

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants