René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"$formatNumber: invalid picture patterns leak raw java.lang.IllegalArgumentException / miss validation (jsonata 2.2.1)","articleBody":"Surfaced while comparing JSONata4Java against the jsonata-js 2.2.1 test corpus during the Jackson 3 migration (#430 / PR #431). These are pre-existing functional-compatibility gaps vs the reference implementation (try.jsonata.org 2.2.1), not regressions introduced by the migration.\n\n`$formatNumber` mishandles several invalid/edge picture strings — either leaking a raw `java.lang.IllegalArgumentException` (rather than a JSONata `EvaluateException`) or producing output the reference rejects.\n\n| Expression | JSONata4Java | jsonata.org 2.2.1 |\n|---|---|---|\n| `$formatNumber(42, \"%%\")` | raw `java.lang.IllegalArgumentException: Too many percent/per mille characters` | error (well-formed JSONata error) |\n| `$formatNumber(42, \"‰‰\")` | raw `java.lang.IllegalArgumentException: Too many percent/per mille characters` | error |\n| `$formatNumber(42, \"%‰\")` | raw `java.lang.IllegalArgumentException: Too many percent/per mille characters` | error |\n| `$formatNumber(42, \"---\")` | returns `\"---42\"` | error (invalid picture) |\n\nExpected: these should raise a proper JSONata `EvaluateException` (D3080-class picture-string error) rather than leaking an internal Java exception or silently accepting an invalid picture.\n\nReference: jsonata-js 2.2.1.","author":{"url":"https://github.com/wnm3","@type":"Person","name":"wnm3"},"datePublished":"2026-07-07T19:05:03.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/437/JSONata4Java/issues/437"}