Hi Gavin,
Clearly, our POC json response for EditPerson is much more verbose :-)
Your example show us that it's possible to reduce number of level in hierarchy
;-)
When I work on documentation/comment/javadoc JsonRenderer, I review what
attribute is really use / usable and so I remove some.
In
Thanks Olivier
You said: When rendering, as JSON flow, for some "field", it's not easily
to say what is only data, what is user presentation data.
Here's a JSON response for A EditPerson Form:
{
"target": "createClient",
"targetWindow": "",
"fields": [
{
"title": "Role Type Id",
Hi Gavin,
Separation completely GUI and application could be exploring, but I think it
will be in a future step.
Currently, one of step which can easily be done is having API for all services
already used by the screen, (the future POST, PUT, PATCH and DELETE)
be able to call them without a scr
