davsclaus opened a new pull request, #74: URL: https://github.com/apache/camel-jbang-examples/pull/74
_Claude Code on behalf of davsclaus_ Companion of apache/camel#26444 for [CAMEL-24744](https://issues.apache.org/jira/browse/CAMEL-24744). The compact notation (`setBody: {simple: "..."}`, `log: "..."`, `to: "..."`, a `when` item with `- simple:`, `script: {groovy: ...}`, `toD: "..."`) is deprecated in Camel 4.23: `camel run` warns about it and `camel validate yaml --canonical` reports it. Every route file the canonical validator flagged (11 of the 43 Camel route files) and the YAML snippets in four READMEs now use the canonical form, with the expression under `expression:` and a step as a map of its options. Comments and block scalars are preserved (the rewrite was done by hand, not with `camel validate normalize`, which drops comments). The three bundled examples — `beginner/tui-hello-world`, `eip/content-based-router`, `observability/message-size` — are byte-identical to the copies shipped in camel-jbang by apache/camel#26444. `AGENTS.md` documents the convention and the validate command. ## Not changed Three files fail the canonical validator for reasons other than the notation, and are left for separate tickets: - `ai/financial-doc-analyzer` — validator false positive on Groovy slashy-string `${...}` interpolation. - `ai/smart-log-analyzer/ui-console/rest-api.camel.yaml` — `rest: {steps: [- get: ...]}` is not valid REST DSL. - `security/pqc-secure-file-transfer` — the bean `script:` has unescaped `"` inside a double-quoted scalar. A CI step running `camel validate yaml --canonical` is a follow-up once Camel 4.23 is released (the CI uses the latest `camel@apache/camel`) and those three are fixed. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
