Closed xinitrc86 closed 4 years ago
what is the expected behavior regarding backwards compatibility?
Inbound body is expected to be camel cased JSON, same as outbound.
I'm not sure how the transformation worked for the response, but if it adds "{DATA:" to i...that is lost.
The serializer offers different options. We could add them to the meta maybe?
none,
low_case,
camel_case,
extended
yea, the change should not break all existing installations
should not break all existing installations
Added usage of /ui2/cl_json to convert from/to camel cased JSON bodies.