You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, after some validation, Peter Ombwa (@peombwa) confirmed that the new implementation when setting ExpandDerivedTypesNavigationProperties to true is generating many invalid/unsupported paths.
Is there a better way to identify which paths should be generated? Should we have a custom annotation so API owners could add it in the API description?
Now that the spec seems applied, it feels like the right path. I don't have the context but it seems to me to be the way forward. What is the broader impact?
Now that the spec seems applied, it feels like the right path. I don't have the context but it seems to me to be the way forward. What is the broader impact?
I have provided more details here regarding use and impact: #378 (comment)
Activity
irvinesunday commentedon Apr 26, 2023
One way of fixing the invalid paths here will involve implementing the new annotations on actions/functions: https://issues.oasis-open.org/browse/ODATA-1538#
Org.OData.Core.V1.ExplicitOperationBindingsOrg.OData.Core.V1.RequiresExplicitBindingThese will help control the generation of operations bound to the derived/OData type cast segments.
This will also help resolve: #232
maisarissi commentedon Apr 27, 2023
Would love to get perspectives from Darrel (@darrelmiller) Sébastien Levert (@sebastienlevert) njaci1
sebastienlevert commentedon Apr 27, 2023
Now that the spec seems applied, it feels like the right path. I don't have the context but it seems to me to be the way forward. What is the broader impact?
irvinesunday commentedon Apr 28, 2023
I have provided more details here regarding use and impact: #378 (comment)