Claus Ibsen created CAMEL-26730:
-----------------------------------
Summary: camel-jbang - AI tools: a literal \n between a value and
the next key is written as a line break, and a file named as a Citrus http body
goes under resource:
Key: CAMEL-26730
URL: https://issues.apache.org/jira/browse/CAMEL-26730
Project: Camel
Issue Type: Improvement
Components: camel-jbang, camel-yaml-dsl, camel-jbang-mcp
Reporter: Claus Ibsen
Fix For: 4.24.0
Follow-ups from the r29 run of the local-model benchmark (qwen3.6, 5 rounds):
* The model wrote the two characters \n after a value where it meant a line
break (expression: "$[...]"\n resultType: java.util.List). The validator says
so and gives the two lines to write, but the model sent the same file again 15,
10 and 16 times in three runs (15 in r28). The write tool now writes the \n as
a line break by itself, when the validator's lines are the old line split at
the \n and the result validates, and says so in its answer. A \n inside quotes,
in block scalars or in code is left alone.
* The Citrus test refusal of CAMEL-26690 put a body that names a file
(classpath:test/sample-order.json) under data:, so the test sent that text. A
body that names a file now goes under resource: file:, the Citrus form for it.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
