Skip to content

docs: fix evalexpr string literal examples in ARCHITECTURE.md - #3723

Open
CryptoJones wants to merge 1 commit into
block:mainfrom
CryptoJones:docs/evalexpr-string-literals
Open

docs: fix evalexpr string literal examples in ARCHITECTURE.md#3723
CryptoJones wants to merge 1 commit into
block:mainfrom
CryptoJones:docs/evalexpr-string-literals

Conversation

@CryptoJones

@CryptoJones CryptoJones commented Jul 30, 2026

Copy link
Copy Markdown

Fixes #3120.

The workflow filter/if examples in ARCHITECTURE.md use single-quoted evalexpr string literals ('P1', 'production'), which evalexpr 11 parses as unbound variable identifiers (VariableIdentifierNotFound), causing conditions to error silently before custom functions are reached.

Changes:

  • Change single quotes to escaped double quotes in the two examples (lines 518, 524)
  • Add a note that evalexpr string literals require double quotes

Verified: YAML code blocks still parse correctly with Python yaml.safe_load.

Proudly Made in Nebraska. Go Big Red! 🌽 https://xkcd.com/2347/

Issue block#3120 reports that the workflow filter/if examples in
ARCHITECTURE.md use single-quoted evalexpr string literals
('P1', 'production'), which evalexpr 11 parses as unbound variable
identifiers (VariableIdentifierNotFound), causing conditions to error
silently before custom functions are reached.

- Change single quotes to escaped double quotes in the two examples
- Add a note that evalexpr string literals require double quotes

Fixes block#3120

Co-authored-by: Aaron K. Clark (CryptoJones) <cryptojones@owasp.org>
Signed-off-by: Aaron K. Clark (CryptoJones) <cryptojones@owasp.org>
@CryptoJones
CryptoJones requested a review from a team as a code owner July 30, 2026 11:32
@cameronhotchkies cameronhotchkies added the triage-ready Appropriate for agentic review label Jul 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

triage-ready Appropriate for agentic review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs: workflow filter/if examples use single-quoted strings, which evalexpr rejects — workflow silently never fires

2 participants