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

   _Claude Code on behalf of davsclaus_
   
   Three tables that said less than they could, found while walking the screens.
   
   - **Beans starts with the beans of the integration.** The scope started at 
`all`. In the circuit-breaker example that was 11 Camel beans (compile post 
processors, variable repositories, the dependency downloader), the same in 
every integration. It now starts at `user`. With none of its own, the table 
says `No beans of its own: f shows the 11 of Camel`. `tui_get_table` gives the 
`scope` and `allBeans`, so an agent knows there are more, and it no longer 
returns nothing when the scope is empty.
   - **Consumers says LAST and LAST FAIL.** SINCE-LAST packed three times into 
one cell, `0s/0s/-` (started, completed, failed). It is now two columns: LAST 
(the last exchange done, `1s ago`) and LAST FAIL (in red, blank when none 
failed).
   - **The numbers of Integrations stand next to the names.** NAME took the 
rest of the width, so on a 200-wide screen the version and the numbers started 
about 80 columns after a short name. NAME is now as wide as the names need, and 
the percentile bar after the timings gets the rest, as in the Routes tab. On a 
narrow screen nothing changes.
   
   The help pages for Beans and Consumers are updated.
   
   Tests: new cases in `BeansTabRenderTest`, `ConsumersTabRenderTest` and 
`OverviewTabRenderTest`. The full `camel-jbang-plugin-tui` suite passes. 
`buildOverviewTable` stays within its `SourceSizeTest` limit. I checked all 
three live with the `fail-well/circuit-breaker` example.
   
   This merges cleanly with #29468, #29486, #29493, #29495 and #29496.
   
   🤖 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