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

   Replaces #28020. That PR was stacked on #28002 (CAMEL-25719), and GitHub 
closed it when the branch of #28002 was deleted at the merge. This is the same 
commit, rebased on main.
   
   ## What
   
   With this and #28002 (merged), all 18 top-level entries of the YAML DSL are 
known to `camel_catalog_doc`, `camel_catalog_find` and `camel_catalog_sample` 
(checked through the MCP server). Before both PRs, 10 were.
   
   - **`interceptFrom` and `interceptSendToEndpoint` have samples.** Their 
examples are on the page of the intercept EIP, after its own. The sample lookup 
now reads that page for them, and keeps the examples that start with their own 
key.
   - **`dataFormats` has a sample.** The documentation had no example of it. 
The data format page of the user manual now shows a data format defined once in 
a top-level `dataFormats` entry, used by `unmarshal` and `marshal` with 
`custom: ref:` (checked with `camel run`: the order is logged pretty printed). 
The sample generator reads that page for `dataFormats`.
   - **`sslContextParameters` is known to `camel_catalog_doc` and 
`camel_catalog_find`.** Its model is an application model of the catalog 
(`models-app`), not an EIP model. It is answered like an EIP now: its options, 
where it goes, and the hint to its sample. `camel_catalog_find` lists it for 
`ssl`.
   
   ## Tests
   
   `CatalogDocsTest` and `CatalogSamplesTest` have a test each. On the rebased 
branch, camel-jbang-core (2531 tests) and camel-jbang-mcp (503 tests) pass, and 
the generated `eip-samples.json` is unchanged by the build.
   
   🤖 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