René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Tracking: unsupported jsonata language features surfaced by the 2.2.1 test corpus","articleBody":"Tracking issue for jsonata language features that JSONata4Java does not yet support, surfaced while comparing against the jsonata-js 2.2.1 test corpus during the Jackson 3 migration (#430 / PR #431).\n\nThese are language/grammar gaps (not simple function bugs) — each likely needs grammar and/or evaluator work. Filed as a single tracking issue rather than one-per-case since they are related \"not-yet-implemented\" gaps vs the reference (try.jsonata.org 2.2.1).\n\n## 1. Inline lambda type signatures\n\nLambda definitions with a type signature are not parsed:\n\n```\nλ($a, $b)\u003cn+n:o\u003e{ ... }\n```\n\nCorpus: `function-signatures/case035`–`case040` (6 cases).\n\n## 2. `~\u003e` function application followed by trailing `[]`\n\nChained function application with a trailing array-selector is not handled:\n\n```\n$data ~\u003e $map($square)[]\n```\n\nCorpus: `higher-order-functions` / `hof-map` case0011.\n\n## 3. Array-sequence construction with trailing `[]`\n\nNested-array / sequence-construction semantics of a trailing `[]` on a path/array constructor:\n\n```\n$.[value, epochSeconds][]\n```\n\nExpected: force the result into a sequence/array per 2.2.1 semantics.\n\n---\n\nReference: jsonata-js 2.2.1. Scope note: these are intentionally out of scope for the Jackson 3 migration PR (#431); this issue captures them for a future compatibility effort.","author":{"url":"https://github.com/wnm3","@type":"Person","name":"wnm3"},"datePublished":"2026-07-07T19:09:48.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/439/JSONata4Java/issues/439"}