davsclaus opened a new pull request, #26607: URL: https://github.com/apache/camel/pull/26607
Replaces #26605, which GitHub closed when its base branch (#26604) was merged and deleted; same two commits rebased on main. The examples tools lagged behind the reorganized examples catalog (CAMEL-24824): `camel_catalog_examples` / `camel_catalog_example_file` in camel-jbang-mcp, `list_examples` / `get_example_file` in the camel-jbang-core AI tool registry, and `tui_list_examples` in the camel-jbang-plugin-tui tool set. - in camel-jbang-mcp the three arguments were not declared optional, so a call without all of them failed with `Missing required argument: filter` (then `level`, then `limit`) - the descriptions still spoke of a difficulty level (beginner, intermediate, advanced) while the catalog now has the 11 group levels, so an agent filtered with values that match nothing - the new metadata (order, teaches, infraServices) was not returned and there was no way to get the groups with their title and intro; the listings came in alphabetical order (ai first) instead of reading order - the core registry capped the result at 20 with no limit argument, so an unfiltered listing dropped half of the 40 examples Now all three listings: - take optional `filter` and `level` (a group); the first two also `limit` (default 50) - return `groups` (level, title, intro, count) and the `examples` in reading order, each with `order`, `teaches` (components, eips, languages, dataformats), `infraServices`, `bundled` and files where the tool had them - describe the groups instead of difficulty levels `ExampleHelper.getTeaches` is the new map accessor; `getTeachesSummary` now builds on it. Tests: `ExampleToolsTest` (new, 3), two cases in `ToolRegistryTest`, one in `TuiToolRegistryLaunchTest`. 🤖 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]
