This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new 68e7ac8a7ce1 chore: fix website build - escape simple expressions in
4.23 upgrade guide
68e7ac8a7ce1 is described below
commit 68e7ac8a7ce14b6d80eb652ad7f6e8af525fa780
Author: Claus Ibsen <[email protected]>
AuthorDate: Thu Sep 24 12:01:01 2026 +0200
chore: fix website build - escape simple expressions in 4.23 upgrade guide
Backticks do not stop attribute substitution in AsciiDoc, so ${body},
${headerfoo}, ${uuidv7} and ${exceptionInfo} were read as references to
missing attributes and dropped from the rendered page. Wrap them in the
+...+ passthrough the file already uses elsewhere.
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Signed-off-by: Claus Ibsen <[email protected]>
---
.../user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_23.adoc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_23.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_23.adoc
index 13789c47d61b..1778be005f4a 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_23.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_23.adoc
@@ -67,8 +67,8 @@ The `range(max)` function now starts at 0, as documented and
as `range` does in
A review of the simple language fixed a number of edge cases. These change
what an existing expression returns:
-* `split` uses the separator as plain text, not as a regular expression:
`${split(${body},'.')}` splits on dots
- (it used to return an empty array), and `${split(${body},'|')}` splits on
the bar. A route that relied on a regular
+* `split` uses the separator as plain text, not as a regular expression:
`+${split(${body},'.')}+` splits on dots
+ (it used to return an empty array), and `+${split(${body},'|')}+` splits on
the bar. A route that relied on a regular
expression separator such as `'\s+'` must use `${body.split('\s+')}` instead.
* The elvis operator `?:` treats any numeric zero as falsy (such as `0L`,
`0.0` or `BigDecimal.ZERO`), not only `0` as
an `Integer`.
@@ -77,7 +77,7 @@ A review of the simple language fixed a number of edge cases.
These change what
string. A `BigDecimal` is a number, so it is not quoted.
* `kindOfType` returns `object` for a `Map` (it used to return `array`).
* A name glued to a function prefix is an unknown function instead of being
read as that function, such as
- `${headerfoo}` (which returned the header `foo`), `${uuidv7}` or
`${exceptionInfo}`. Use `${header.foo}`.
+ `+${headerfoo}+` (which returned the header `foo`), `+${uuidv7}+` or
`+${exceptionInfo}+`. Use `${header.foo}`.
* A hidden file name has no extension: for `.bashrc` then `${file:name.ext}`
is `null` (it used to be `bashrc`), and
for `.route.yaml` then `${file:name.noext}` is `.route`. This comes from
`FileUtil.onlyExt` and `FileUtil.stripExt`.
* The chain operator `~>` needs a space on both sides, as the other operators
do, so `A~>B` is text.
