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

   https://issues.apache.org/jira/browse/CAMEL-25372
   
   Two YAML structure mistakes from the local-model benchmark (r5, steps that 
used all 20 tool calls), and what the validator says now.
   
   **A top-level key without its `- `**: the model appended `errorHandler:` at 
column 1 after the `- route:` entries.
   
   - Before: `line 41 is not YAML ("errorHandler:"): a route file holds only 
the YAML, put explanations in a # comment or leave them out`
   - Now: `line 41: errorHandler: is a top-level key in a file whose entries 
are list items (- route:, ...): write it as a list item, - errorHandler:, and 
indent the lines under it two spaces more, as the - route: entries are`
   
   Prose appended to a file is still reported as before; the integration test 
`ValidatePluginITCase` appends `test`.
   
   **An option at the column of its EIP**: `parameters:` under `- to:`, at the 
column of `to:`. The model wrote this three times.
   
   - Before: `must have at most 1 properties (a step is one EIP: an option of 
that EIP is indented under its key, and the next EIP is its own - item)`
   - Now: `must have at most 1 properties (parameters: is at the column of - 
to: as an option of to it is indented under to:, two spaces more, next to its 
other options)`
   - Another EIP in the same place: `to: is another EIP: start it as its own 
item, - to:`
   - A key that is neither an option of the EIP nor an EIP keeps the general 
sentence.
   
   `YamlValidator.optionsOf(eip)` reads the EIP's options from the YAML DSL 
schema.
   
   Tests: `StructureHintTest` (3). The validator suite passes (217), and so 
does camel-jbang-core, which uses the messages (1510).
   
   🤖 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