[Ocs] Proposal for new field in CONTENT module

[Dan Leinir Turthra Jensen]

On Friday 17 August 2012 15:55:21 Laszlo Papp wrote:
> > My issue is that with your approach in certain cases, I would need to make
> > a lot of queries to get all the necessary content data I am interested in.
> > Having explicite queries and also embedded pointers would be a compromise
> > (I can help with that, and work out in addition to this proposal, if
> > accepted).
> 
> I would like to clarify myself shortly: it means a +1 from my side into
> 1.7, if the specification users will also be able to fetch everything
> needed in a bunch (i.e. my proposal for that). Then, this feature would be
> well-covered and widely useful, in my opinion.
> 
> Laszlo

  Well... how about an option on content/list and content/get to expand the 
requires from the listing of IDs into a full content item listing? The 
specific idea being to do this in the two calls:

* URL Argument: fullrequires - Defaults to false. Set to true, this will cause 
the listing to include full content items for any requiredby and requires 
fields in the items. If the content item required has already been listed at a 
higher level in the same returned data, it will not be shown again.

-- 
..Dan // Leinir..
http://leinir.dk/

                          Co-
                            existence
                          or no
                            existence

                          - Piet Hein