Navigation property not automatically routed, requires custom route declaration about swashbuckle.odata HOT 5 CLOSED

The approach to support this feature would be similar to #44.

from swashbuckle.odata.

I just want to also point out that [ODataRoute(..)] also destroys the /$count path suffix feature in Microsoft's OData v4 implementation (particularly considering /$count also measures the count of where ?$filter=..&$expand=..&$select=.. are used), so resolving this is going to be mandatory unless using instead the earlier OData feature of ?$count=true and reading the @odata.count off the payload. I realize it's on our plate(s), just pointing out that [ODataRoute(..)] is not a completely viable workaround.

from swashbuckle.odata.

I've tried the [ODataRoute("...] WorkAround but we also have a routePrefix/{Parameter} and the parameter is not being picked up as required by swashbuckle.odata

from swashbuckle.odata.

Closing this old feature request as it is not important enough for someone to spend the time to implement it.

from swashbuckle.odata.

I was not aware that there was some kind of time frame for which a requested feature needs to be implemented. I suppose if I end up getting to this I'll create a new feature request.

from swashbuckle.odata.