This is an automated email from the ASF dual-hosted git repository. luigidemasi pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel.git
commit efe1577aaa616d0a7c155bac846cb31889ee9120 Author: Luigi De Masi <[email protected]> AuthorDate: Wed Oct 7 16:31:32 2026 +0200 CAMEL-25382: Preserve literal braces in semantic documentation Protect inline placeholder-escaping examples from AsciiDoc substitutions. This fixes the missing attribute warning in PR documentation validation and preserves the closing escape backslash shown in the YAML example. Regenerate the catalog documentation mirror. Co-authored-by: Codex <[email protected]> Signed-off-by: Luigi De Masi <[email protected]> --- .../resources/org/apache/camel/catalog/docs/semantic-language.adoc | 4 ++-- .../camel-ai/camel-semantic/src/main/docs/semantic-language.adoc | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/semantic-language.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/semantic-language.adoc index 5083db4bc638..699f055934d8 100644 --- a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/semantic-language.adoc +++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/semantic-language.adoc @@ -127,8 +127,8 @@ For example, a nested expert policy can externalise its cutoff without convertin ---- String parameters, including prompts, use Camel property placeholder escaping for literal braces. -For example, YAML `instructions: 'Explain \{{example\}}'` gives the expert `Explain {{example}}`. -In Java, use `.parameter("instructions", "Explain \\{{example\\}}")` for the same literal text. +For example, YAML `+instructions: 'Explain \{{example\}}'+` gives the expert `+Explain {{example}}+`. +In Java, use `+.parameter("instructions", "Explain \\{{example\\}}")+` for the same literal text. Camel validates recognised parameter names, required values, types and declared constraints. The expert checks operation-specific combinations and compatibility with its bean configuration. diff --git a/components/camel-ai/camel-semantic/src/main/docs/semantic-language.adoc b/components/camel-ai/camel-semantic/src/main/docs/semantic-language.adoc index 5083db4bc638..699f055934d8 100644 --- a/components/camel-ai/camel-semantic/src/main/docs/semantic-language.adoc +++ b/components/camel-ai/camel-semantic/src/main/docs/semantic-language.adoc @@ -127,8 +127,8 @@ For example, a nested expert policy can externalise its cutoff without convertin ---- String parameters, including prompts, use Camel property placeholder escaping for literal braces. -For example, YAML `instructions: 'Explain \{{example\}}'` gives the expert `Explain {{example}}`. -In Java, use `.parameter("instructions", "Explain \\{{example\\}}")` for the same literal text. +For example, YAML `+instructions: 'Explain \{{example\}}'+` gives the expert `+Explain {{example}}+`. +In Java, use `+.parameter("instructions", "Explain \\{{example\\}}")+` for the same literal text. Camel validates recognised parameter names, required values, types and declared constraints. The expert checks operation-specific combinations and compatibility with its bean configuration.
