This is an automated email from the ASF dual-hosted git repository.

cbrisson pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/velocity-site.git

commit 303ac439b827dcfdcbacc5a508b09e0670d22c2d
Author: Claude Brisson <[email protected]>
AuthorDate: Sun Aug 25 17:06:59 2024 +0200

    Document the '1'=='1.0' fix in the upgrading page
---
 src/content/engine/devel/upgrading.mdtext | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/content/engine/devel/upgrading.mdtext 
b/src/content/engine/devel/upgrading.mdtext
index 9c4532c..01b4ea6 100644
--- a/src/content/engine/devel/upgrading.mdtext
+++ b/src/content/engine/devel/upgrading.mdtext
@@ -50,6 +50,7 @@ Also, please note that since version 2.1, Velocity requires 
Java JDK 1.8+ for bu
 
 ### VTL Changes
 
++ The comparison `'1' == '1.0'` was returning true since Velocity 2.0 because 
of an overzealous String to Number conversion, which also had a performance 
impact. If a template relies on such a behaviour, it will need to be fixed.
 + With the `runtime.immutable_ranges=false` configuration, the VTL range 
operator `[x..y]` returns a mutable list.
 
 ## Upgrading from Velocity 2.2 to Velocity 2.3

Reply via email to