Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Child Collections of ODataController in Swagger UI #67

Closed
nealeduncan opened this issue Feb 9, 2016 · 2 comments
Closed

Child Collections of ODataController in Swagger UI #67

nealeduncan opened this issue Feb 9, 2016 · 2 comments

Comments

@nealeduncan
Copy link

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?

@bigred8982
Copy link
Contributor

I believe this is related to #58

@ghost ghost added the duplicate label Feb 9, 2016
@ghost
Copy link

ghost commented Feb 9, 2016

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.)

Closing this as a duplicate of #58.

@ghost ghost closed this as completed Feb 9, 2016
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants