[OASIS Issue Tracker] (ODATA-1018) Allow $expand and $select with modifying requests that return a collection in combination with return=representation to specify the response shape

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/ODATA-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=64934#comment-64934 ] 

Michael Pizzo commented on ODATA-1018:
--------------------------------------

$expand and $select might be okay, but $filter is already used in some cases for set operations.

For example:
PATCH Employees?$filter=ReviewScore gt 9
{
    "Status":"SuperStar"
}

Is it weird to say that $expand and $select refer to the results, but $filter refers to the operation? Would someone expect $filter to apply to the results if $expand and $select apply to results?  I guess in this case it would apply to the results as well as the operation, but consider:

PATCH Employees?$filter=ReviewScore gt 9
{
    "ReviewScore": 8
}

In this case $filter would be applied to the operation to change everyone with a review score greater than 9 to 8, but if it was applied to the results the results would (necessarily) be empty.


> Allow $expand and $select with modifying requests that return a collection in combination with return=representation to specify the response shape
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-1018
>                 URL: https://issues.oasis-open.org/browse/ODATA-1018
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol, OData URL Conventions
>    Affects Versions: V4.0_OS
>            Reporter: Hubert Heijkers
>              Labels: Usability
>             Fix For: V4.01_CSD02
>
>
> This is a clone of ODATA-614 in which we allowed to use $expand and $select already for single entities.
> While discussing this in our meeting on December 1st, we concluded that there is no reason to not allow this for collections either.
> The proposed solution is pretty much just allowing what we already allowed for requests returning a single resource to collections as well. Re-reading the proposal though I wonder if it is obvious that returning 'No Content' implies it couldn't return what was requested but still executed the request. I'm not proposing to fail the request just not sure if the response is in line with what one expects/what a GET request would do if it were asked the same???



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)