[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-1074) Support Functions with /$each and define the representation for collection-valued actions and functions with /$each
Michael Pizzo created ODATA-1074: ------------------------------------ Summary: Support Functions with /$each and define the representation for collection-valued actions and functions with /$each Key: ODATA-1074 URL: https://issues.oasis-open.org/browse/ODATA-1074 Project: OASIS Open Data Protocol (OData) TC Issue Type: Bug Components: JSON Format, Protocol, URL Conventions Affects Versions: V4.01_CSD02 Environment: [Proposed] Reporter: Michael Pizzo Fix For: V4.01_CSD02 Since we added the support to use /$each with actions, we have to define what the result looks like. It seems reasonable that the result is an array of action results. What, then, is the shape of the result if the action returns a collection? In order to be annotated with things like count and next link, the result would have to be a collection of value arrays, as in: {"value":[{"value":[{a=1,b=2},{a=2,b=3}]},{"value":[{a=4,b=5}]}]}. Once we have defined the result of /$each for actions that return results, it seems natural that we support /$each with functions as well. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]