davsclaus opened a new pull request, #28193: URL: https://github.com/apache/camel/pull/28193
Stacked on #28192. The table of the processors in the Routes view showed the id of each step. An id Camel generates (`to1`, `setBody2`) only repeats the type in the column before it, as Claus noticed in the screenshot of #28192.  The table now shows: - **TYPE** indented by level, so the tree of the steps shows there (the steps of a choice branch under the choice). - **LINE**: the line of the route source the step is on, from the source location the status file already has. The column is only there when the runtime records source locations. - **PROCESSOR**: what the step does, as the route structure has it and the diagram shows it. - Examples: `log:outbox` for `to[log:outbox]`, `jackson` for `unmarshal[jackson]`, the expression of a `setBody`. - The structure is the one the diagrams already ask for. The Routes tab asks for it again only when the routes change, on the background thread. - Until it is there, a step that sends shows where it sends to. - An id the route sets (`id: audit-fanout`) is shown first. Camel generates ids as the type with a counter (the node prefix of a route template or kamelet in front), and those are left out. Top mode shows the line and what the steps do as well. It sorts by time, so it has no tree. PROCESSOR gets its room (30 columns) before BODY TYPES. The body types are cut first, as the Info panel of the diagram has them in full. **Tests:** `RoutesProcessorLabelsTest` covers the table and Top mode, with and without the route structure, the line of a source location, and which ids the route sets. The 2201 tests of the module pass. The screenshot is from a scratch `camel tui` against an integration that runs on the jars of the branch. It replaces the Routes screenshot that #28192 added to the manual's diagram page. _Claude Code on behalf of davsclaus_ 🤖 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]
