Fixing invalid JSON formatting for nested REST Views

[patrickkaleta]

Some time ago we discussed the possibility to define REST Views (here), which would allow to provide only the desired fields of a content type and even fields of referenced entities by using nested REST Views (idea was to minimalize number of needed REST calls and the size of the payload). This could now be interesting e.g. for sharing content between CSIS and the marketplace via REST (issue).

Nesting REST Views can be achieved by including a REST view inside another REST view. But the problem was that this nested view wasn't properly formatted (a problem in the Core REST module). Example below shows wrong formatting for field_analysis_context, which is another nested View.



@fgeyer16 found a module, which fixes this bug and creates proper JSON objects with nested REST Views. This module is currently only available in Alpha, but I tested it locally and it seems to be working as expected (even with double-nested Views :-) ).

[p-a-s-c-a-l]

Is this module now used / still needed in our public CSIS instance?

[patrickkaleta]

It is currently not used nor installed and not needed as long as all external services are ok with making multiple REST calls to get what they want. Personally, I'd like to avoid using it since it's still alpha, not very actively developed and not used on many sites.