davsclaus opened a new pull request, #29511: URL: https://github.com/apache/camel/pull/29511
_Claude Code on behalf of davsclaus_ Found by running the examples. The What happened strips on About were in the order the integration lists its routes, which is by id. - In `route/enrich-and-dedupe`, `audit` came before `incoming-orders`, the route everything starts with. - In `route/dynamic-routing`, the entry route `incoming-orders` was the third strip of eight, between `billing-pending` and `invoice-backup`. The strips now follow the Routes panel above them, where a route comes after the one that calls it, then any running route the panel does not have. Test: `AboutViewTest#theStripsAreInTheOrderOfTheRoutesACalledRouteAfterItsCaller`. The full `camel-jbang-plugin-tui` suite passes, apart from `ConfigurationTabRenderTest`, which fails on main and is fixed by #29503. One more finding I left out: the Routes panel marks a route called through a `wireTap` with `↳`, a call that waits, though a wire tap does not wait (`⇢`). The link kind comes from camel-jbang-core's `ProjectOverview`, which knows the scheme of the endpoint (`direct`) but not the EIP that sends to it. Fixing it means threading the EIP through the YAML, XML and Java parsers there, which also serve `camel get about`. 🤖 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]
