Skip to content

Commit 43cc18a

Browse files
committed
Use literal monospace in SpEL templating section
Prior to this commit, the text `#{ }` was displayed as { } with a bright green background. This commit addresses this by making use of Asciidoc's literal monospace feature: `+#{ }+`.
1 parent 4d5536d commit 43cc18a

File tree

1 file changed

+2
-2
lines changed
  • framework-docs/modules/ROOT/pages/core/expressions/language-ref

1 file changed

+2
-2
lines changed

framework-docs/modules/ROOT/pages/core/expressions/language-ref/templating.adoc

+2-2
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33

44
Expression templates allow mixing literal text with one or more evaluation blocks.
55
Each evaluation block is delimited with prefix and suffix characters that you can
6-
define. A common choice is to use `#{ }` as the delimiters, as the following example
6+
define. A common choice is to use `+#{ }+` as the delimiters, as the following example
77
shows:
88

99
[tabs]
@@ -32,7 +32,7 @@ Kotlin::
3232
======
3333

3434
The string is evaluated by concatenating the literal text `'random number is '` with the
35-
result of evaluating the expression inside the `#{ }` delimiters (in this case, the
35+
result of evaluating the expression inside the `+#{ }+` delimiters (in this case, the
3636
result of calling that `random()` method). The second argument to the `parseExpression()`
3737
method is of the type `ParserContext`. The `ParserContext` interface is used to influence
3838
how the expression is parsed in order to support the expression templating functionality.

0 commit comments

Comments
 (0)