You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be cool if incoming JSON based request or response bodies could be bound to a projection interface with the accessor methods defaulted to customizable JSON Path expressions:
{"firstname" : "…","lastname" : "…", … }
To access this data, this projection interface is sufficient:
By default the accessor would just be interpreted as direct nested properties. However, if the JSON Path expressions are customized to be more lenient, e.g. $..firstname. the payload can even change to this and the client would still work:
{"user" : {"firstname" : "…","lastname" : "…"}}
This is a concept very much inspired by XMLBeam. We might consider dropping our support in favor of a JSON variant of it in the future
Oliver Drotbohm opened DATACMNS-885 and commented
It would be cool if incoming JSON based request or response bodies could be bound to a projection interface with the accessor methods defaulted to customizable JSON Path expressions:
To access this data, this projection interface is sufficient:
By default the accessor would just be interpreted as direct nested properties. However, if the JSON Path expressions are customized to be more lenient, e.g.
$..firstname
. the payload can even change to this and the client would still work:This is a concept very much inspired by XMLBeam. We might consider dropping our support in favor of a JSON variant of it in the future
No further details from DATACMNS-885
The text was updated successfully, but these errors were encountered: