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
Yes, when #58 is implemented you can turn this 'feature' off.
We got where we are today from this thought process.
In summary:
Currently in the OData swagger model, by default we are displaying only top level primitive values to reflect what you will actually get back from OData if you don't do an $expand. (In WebApi, on the other hand, you will get back the full serialized graph, so by default we display the full graph in the WebApi swagger model. There is no 'expand' concept.)
Child collections are not shown for ODataControllers.
In the example here: http://swashbuckleodata.azurewebsites.net/swagger/ui/index
The Customers ODataController resource does not show that in the GET, that Orders is available. It only shows primitive types (string, int etc).
The ApiController resource shows child resources (in the example Projects is a child collection of Client GET ApiController).
Can child collections be added to ODataControllers please?
The text was updated successfully, but these errors were encountered: