[
https://issues.apache.org/jira/browse/CAMEL-25200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18121273#comment-18121273
]
Brijesh Thakkar commented on CAMEL-25200:
-----------------------------------------
[~davsclaus]
Before I start, a few design questions:
1. Scope. camel validate runs the body check per file, camel overview works
across the whole project. Should overview analyse per file (so the two
never disagree) or project-wide (more accurate across files, may differ
from validate for routes called from another file)?
2. Shared code. I'd move the dead-letter/saga handler collection and the
direct:// endpoint normalisation into BodyTypeFlow itself, so both callers
agree. This changes camel validate's output slightly: it drops a false
body-never-set for dead-letter/saga routes and adds one for direct://x
callers it missed. OK in the same PR as a separate commit, or a separate
PR first?
3. Schema gate. validate only runs the body check on files that pass schema
validation. Should overview apply the same gate, or report regardless?
Plan: YAML only, a new "Message bodies" section in the markdown, bodyFrom in
the JSON, no change to the Routes table.
> camel-jbang - camel overview: show where each route's message body comes from
> and report body-never-set
> -------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-25200
> URL: https://issues.apache.org/jira/browse/CAMEL-25200
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Brijesh Thakkar
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
