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

   ## Summary
   
   - Include README files (`.md`, `.adoc`) when running integrations via `camel 
run`, tracked via `camel.jbang.readmeFiles` property and exposed in status JSON
   - Add **Show Documentation** to the F2 actions menu — lists running 
integrations with README files, fetches content via the new `readme` action, 
and renders with TamboUI's `MarkdownView` widget
   - Add **`d` key** in the example browser to view README docs for any 
example: bundled examples load from JAR resources, online examples download 
from GitHub (tries `.md` first, falls back to `.adoc`)
   - Convert all bundled example READMEs from AsciiDoc to Markdown for proper 
rendering
   - Include AsciiDoc-to-Markdown converter (`DocHelper`) for online `.adoc` 
fallback
   - Auto-select first row in circuit breaker tab when switching to it
   
   ## Test plan
   
   - [ ] Run `camel run` with an example that has a README file, verify the 
README is included via `camel get` status
   - [ ] Open TUI (`camel monitor`), press F2 → "Show Documentation" → verify 
running integrations with READMEs are listed
   - [ ] Select an integration from the doc picker → verify README content 
renders in MarkdownView
   - [ ] Press F2 → "Run an example" → select a bundled example → press `d` → 
verify README displays
   - [ ] Press `d` on an online example → verify README downloads and displays
   - [ ] Press Esc in doc viewer opened from example browser → verify it 
returns to example browser
   - [ ] Press 9 for circuit breaker tab with data → verify first row is 
auto-selected
   - [ ] Verify AsciiDoc content (headings, code blocks, links) renders cleanly 
through the converter
   
   🤖 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]

Reply via email to