[
https://issues.apache.org/jira/browse/TAP5-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681920#comment-17681920
]
Ben Weidig commented on TAP5-2747:
----------------------------------
Don't worry, you didn't discourage me.
We've developed many "missing" Tapersty features over the years in our product,
but that doesn't mean they have merit in Tapestry itself; not everyone has the
same use and edge cases as us.
I'd have just committed a smaller, more inconsequential feature if it's fully
tested.
A JSON lookup syntax, however, is a more significant decision that can't be
changed once released without upsetting users.
That's why I prefer having someone arguing against a feature of mine because it
might reveal alternative approaches (JsonPath) or edge cases (negative array
indices, like JsonPath).
> KeyPath-based traversal of JSONCollection
> -----------------------------------------
>
> Key: TAP5-2747
> URL: https://issues.apache.org/jira/browse/TAP5-2747
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-json
> Affects Versions: 5.8.2
> Reporter: Ben Weidig
> Assignee: Ben Weidig
> Priority: Minor
>
> As navigation nested {{JSONObject}} structures can be tedious, so I propose
> adding a String-based KeyPath traversal system.
> For example:
> {code:java}
> JSONObject json = ...
> // {
> // outer: { inner: "here" },
> // array: [
> // 1,
> // { innerArray: ["A", "B", "C"] },
> // ["Z", "Y", "X"]
> // ]
> // }
> var result = json.getByKeyPath("array[1].innerArray[5]?");
> // Equivalent to
> var result = json.getByKeyPath("array.[1].innerArray.[5]?");{code}
>
> The {{getByKeyPath}} method returns an Object, but the other types are
> available, too.
> The following types of keypaths should be supported:
> * {{JSONObject}} navigation, e.g. {{outer.inner -> "here"}}
> * {{JSONArray}} indices, e.g. {{array[0] -> 1}}
> * {{JSONArray}} indices without key, e.g. {{array.[0] -> 1}}
> * Optionality, e.g, {{outer.nonExistant? -> null}}
> The different types are combinable as needed.
> By default, the KeyPath is delimited by "." but there should also be a
> {{getByKeyPath(String getKeyPath, String delimiter)}} to support "." in JSON
> keys.
> I already have a proof-of-concept working. However, it requires some cleanup
> and a lot of testing before being ready.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
