davsclaus opened a new pull request, #26377:
URL: https://github.com/apache/camel/pull/26377
A new shared authoring tool, `camel_catalog_sample`: validated YAML samples
of an EIP or a file entry (`onException`, `aggregate`, `circuitBreaker`,
`split`, `rest`, `beans`, `routeConfiguration`, ...) by name, kebab-case, a
part name (`onFallback`, `when`) or what to do ("read file", "call service",
"batch", "retry", "router"), with where it goes: a top-level entry next to
`route`, or a step inside `steps`.
The samples come from the catalog's own documentation for the Camel version
in use (`camel_catalog_doc` style lookup of the `<name>-eip` page, every
`[source,yaml]` block validated at lookup), so they are version-accurate; a
shipped set (`eip-samples.json`, extracted from the docs and validated) is the
fallback for the user-manual pages the catalog does not bundle. A `beans` entry
has samples (a model that had just been told "beans is a list" asked for it and
got nothing).
Why: in the benchmark a local model nested `onException` inside a route, was
refused by the schema, looked the EIP up in the catalog, and learned every
option and nothing about where it goes; it gave up after seven minutes. With
this tool that step became three calls. The same question ("what does a correct
one look like") is what a person asks the docs.
Tests: `CatalogSamplesTest` (9), `AuthoringToolsTest` (core and mcp). 6
files, most of the lines the JSON.
Follow-ups noted on CAMEL-24693: the shipped set generated by a mojo in
camel-jbang-core's build; the EIP pages are guarded by #26375.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01Bp3538HRBPMQkb5ta9xRaj
--
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]
