Bound actions and function overloads via container and structured type #233
Conversation
We don't have all these examples for the other cases either. Let's discuss this in the TC. |
Yes. |
HeikoTheissen
changed the title
| Complex Type|have the type or a subtype thereof | ||
| Entity Type|have the type or a subtype thereof |
There was a problem hiding this comment.
MySchema.MyEntityType/MySchema.MyAction(MySchema.MyEntityType)
is equivalent to MySchema.MyAction(MySchema.MyEntityType) but
MySchema.MyEntityType/MySchema.MyAction
has a meaning of its own. Is it OK to allow both?
|
What about targets like ? |
| A binding parameter is "addressed via a resource path" if the path expression addressing the | ||
| binding parameter starts with the resource path, it may then continue with segments | ||
| described in [OData-URL](#ODataURL), sections 4.6 through 4.12. If the resource path | ||
| addresses a collection, the binding parameter can also be a single instance of that | ||
| collection if a segment described in [OData-URL](#ODataURL), sections 4.9 and 4.10, follows. |
There was a problem hiding this comment.
Does the annotation target
MySchema.MyContainer/MyEntitySet/MySchema.MyAction
address the bound action
POST MyEntitySet/MySchema.MyComposableFunction()/MySchema.MyAction
even if the composable function returns a different entity set?
There was a problem hiding this comment.
I would expect that it does not, instead I'd expect that annotations for target
MySchema.MyContainer/MyOtherEntitySet/MySchema.MyAction apply if function MySchema.MyComposableFunction returns entities from MyOtherEntitySet.
There was a problem hiding this comment.
instead I'd expect that annotations for target
MySchema.MyContainer/MyOtherEntitySet/MySchema.MyActionapply if functionMySchema.MyComposableFunctionreturns entities fromMyOtherEntitySet.
Which is the case according to the first table row:
| Model element | means the binding parameter must be |
|---|---|
| Entity Set | an instance or collection of instances from the entity set |
There was a problem hiding this comment.
But the target
MySchema.MyContainer/MyOtherEntitySet/MyContainmentNavigationProperty/MySchema.MyAction
would not apply if the composable function returned entities from the contained entity set.
Must we distinguish between containment and non-containment navigation properties? Currently we have only
| Model element | means the binding parameter must be |
|---|---|
| Navigation Property via container | addressed via a resource path to the navigation property |
There was a problem hiding this comment.
If the function returns totally unrelated entities, we can't express that (yet) in $metadata.
If the function returns related entities and is defined with
EntitySetPath="__it/_otherEntity/MyContainmentNavigationProperty"then the client could figure out look for annotations with target
MySchema.MyContainer/MyOtherEntitySet/MyContainmentNavigationProperty/MySchema.MyAction
That is asking a lot, and I feel we are down a very exotic rabbit hole.
https://issues.oasis-open.org/browse/ODATA-1626
Path evaluation rules are already covered by the paragraph