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

   Layout fixes to the camel-jbang monitor's tables, one commit each.
   
   **Overview**
   - At 100 columns the NAME column was dropped, so apps showed by PID only. 
NAME now keeps room for a name: the timings, the rate and the version give way 
first.
   - A name that does not fit ends with an ellipsis. Before, an opened 
project's "(project)" suffix was cut silently.
   
   **Routes**
   - TOTAL and FAIL are as wide as their longest value. They were cut before 
the closing parenthesis: "3 (18m30s".
   - The timing columns are fixed, so the URI column gets the rest of the width.
   - Route ids, URIs and processor ids end with an ellipsis where they are cut.
   
   **Errors**
   - The exchange id is short, as on the Activity tab, so MESSAGE has room 
("card dec" became "card declined"). The detail below shows the full id.
   - COUNT shows 1 for an error seen once.
   
   **Empty tables**
   - A table that is empty said so in its first column, which cut the message 
where that column is narrow ("No infligh"). It now says so in the widest column.
   
   **Consumers**
   - TYPE was empty on every row: the status names the class `clazz`, which the 
monitor did not read. Producers had the same problem.
   - REMOTE uses the check mark the Endpoints tab uses for the same flag.
   - Long ids and URIs end with an ellipsis.
   
   **Open Project dialog**
   - It is up to 100 columns wide. A remembered folder was cut at its start.
   
   Each change was checked on screen at 150 and 100 columns. All 1777 tests of 
the monitor plugin pass.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   
   https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m


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