davsclaus opened a new pull request, #28151: URL: https://github.com/apache/camel/pull/28151
https://issues.apache.org/jira/browse/CAMEL-25870 Four validator messages did not help a coding agent fix the route, in a night of runs against a local model: 1. **A language written as a step.** `- simple: "${body}"` got "did you mean 'sample'?". Now: "'simple' is a language, not a step: an expression is written in a step that uses it, such as `- setBody: {expression: {simple: {expression: "${body}"}}}`, or `- filter: ...`". 2. **A key in the column of the dashes of a list.** For example, `steps:` under the `- simple:` of a `when:`, or `onFallback:` under the `- to:` of a circuit breaker. This got the raw parser message "expected <block end>, but found '?'". Now the message names the two columns to choose from: the column of the item's keys, and the column of the key that holds the list. 3. **A step written as a plain name.** `- stop` got "string found, object expected". Now: "a step is a key followed by its options: write `- stop: {}`". For a step with a short string form, the property is named: `- to: {uri: "..."}`. 4. **The `${...}` in a constant hint.** It swapped double quotes for single quotes, so `{"error": ...}` became `{'error': ...}`, which is not JSON, and the agent copied it. Now the text is quoted as written, in single quotes when it holds a double quote. The hint "${...} is simple syntax, not groovy" uses the same quoting. Tests: camel-yaml-dsl-validator 267 pass (4 new tests, and the updated ConstantWithSimpleTest). camel-jbang-core 2360 + 237 pass with this validator. Its one LogConfigurationTest flake is the test-order issue fixed by #28146. _Claude Code on behalf of davsclaus_ 🤖 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]
