davsclaus opened a new pull request, #23511:
URL: https://github.com/apache/camel/pull/23511

   ## Summary
   
   Normalizes 99 YAML DSL code blocks across 46 documentation files from 
classic shorthand form to canonical (normalized) form, consistent with the 
canonical JSON schema introduced in CAMEL-22987.
   
   **Four shorthand patterns were normalized:**
   
   1. **Shorthand `to:`** — `- to: "direct:foo"` → expanded to `- to:` with 
nested `uri:` field
   2. **Inline `simple:` expression** — `simple: "${body}"` → wrapped with 
`expression:` / `simple:` / `expression:` canonical structure
   3. **URI with inline query params** — `uri: "file:inbox?move=../backup"` → 
split into `uri: file:inbox` + `parameters:` block
   4. **Bare `from:` without `route:` wrapper** — `- from:` → wrapped with `- 
route:` parent
   
   **Scope:**
   - 33 EIP documentation pages 
(`core/camel-core-engine/src/main/docs/modules/eips/pages/`)
   - 13 user manual pages (`docs/user-manual/modules/ROOT/pages/`)
   
   **Edge cases handled:**
   - `RAW()` syntax in passwords (e.g., `RAW(se+re?t&23)`) — `&` inside `RAW()` 
is not a param separator
   - Property placeholders with `?` inside (e.g., `{{myQuery?nested=false}}`) — 
not a query param separator
   - `pollEnrich`/`enrich` EIPs use `expression:` for endpoint URIs, not 
`uri:`/`parameters:`
   - `endpoint.adoc` has an intentional "YAML::" vs "YAML expanded::" contrast 
showing both compact and decomposed forms — the compact form was preserved
   
   **Not in scope (intentionally):**
   - Component documentation pages
   - Upgrade guide pages
   
   ## Test plan
   
   - [ ] Spot-checked representative YAML blocks with `camel validate yaml-dsl` 
(MCP schema validation)
   - [ ] Verified no YAML blocks that intentionally demonstrate shorthand 
syntax were normalized
   - [ ] Documentation-only change — no code changes, no test impact
   
   _Claude Code on behalf of Claus Ibsen_
   
   Co-Authored-By: Claude Opus 4.6 <[email protected]>


-- 
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]

Reply via email to