preserve escaped CEL literals during lifting - #54
Open
liby wants to merge 1 commit into
Open
Conversation
liby
force-pushed
the
fix/preserve-cel-string-escapes
branch
from
August 12, 2026 06:23
c7ff2c8 to
7c084ba
Compare
liby
force-pushed
the
fix/preserve-cel-string-escapes
branch
from
August 12, 2026 06:24
7c084ba to
9c0915f
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
liftLiteralsstores string arguments as slices of the original CEL source. For escaped literals, the lifted variable therefore contains escape syntax rather than the decoded CEL value.Skip literal lifting for expressions that contain a backslash, leaving CEL parsing, escape decoding, and validation to cel-go across standard, raw, bytes, and triple-quoted strings. Expressions without backslashes keep the existing normalization and cache path.
Add direct-versus-cached parity coverage for escaped strings and ensure invalid CEL escapes remain parse errors.
Fixes #53