Refactor: Pass ActivationInterface to CEL function implementations #1763
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
copybara-service
bot
force-pushed
the
test_823026720
branch
6 times, most recently
from
aafa36e to
0d6d09f
Compare
This change modifies the `cel::Function::Invoke` signature to include a nullable `cel::ActivationInterface*`. This allows custom CEL function implementations to access the current activation context. PiperOrigin-RevId: 823026720
copybara-service
bot
force-pushed
the
test_823026720
branch
from
0d6d09f to
54676db
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Refactor: Pass ActivationInterface to CEL function implementations
This change modifies the
cel::Function::Invokesignature to include a nullablecel::ActivationInterface*. This allows custom CEL function implementations to access the current activation context.