davsclaus commented on PR #27100:
URL: https://github.com/apache/camel/pull/27100#issuecomment-5910105380

   Thanks for all the work on this, @Brijesh-Thakkar. Since this PR was opened, 
`camel overview` (CAMEL-25143, #27103) has been merged. It covers most of what 
`camel topology` offers, and more:
   
   - It reads **YAML, XML and Java** routes (this PR is YAML only).
   - It links routes over `direct`/`seda`/brokers, including error-handler 
links, and lists external systems and entry points (markdown or JSON).
   - Its findings include a `direct:` endpoint nothing consumes 
(`missing-route`), a route nothing calls (`unreferenced`), cycles, duplicate 
ids, missing descriptions and pass-through routes.
   - It also feeds `camel-summary.md`, the MCP tools and the TUI architecture 
view.
   
   So we don't want a second top-level command with almost the same purpose. 
I'm marking this PR as **draft, pending close**.
   
   The part that is genuinely new here is the **body-origin analysis**: where 
each route's body comes from, and the first step that may set it. That would be 
very welcome in `camel overview`, as a per-route "body from" line plus a 
`body-never-set` finding, reusing the validator's `BodyTypeFlow` so the 
overview and `camel validate` never disagree. We are also looking at how `camel 
overview` can share more of the validator's analysis in general. If you are 
interested in taking the body-origin part into `camel overview`, a new PR 
against it would be great.
   
   
   _Claude Code on behalf of davsclaus_


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