-
Notifications
You must be signed in to change notification settings - Fork 97
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
Different gateway swagger response json than service swagger #203
Comments
Hi, it's from Ocelot Aggregates, or from standard service? If its from aggregation then looks similar like issue #191 |
It is not from aggregates. It is just a standard downstream service configured with Routes. |
Can you please prepare simple reproducible example. Because it's OK on my projects. |
Hi, It seems rendering of circular-referenced objects on Swagger UI is still an ongoing issue. However, a comment on this issue seemed to work for me! For our case, to make the paths of the downstream Swagger endpoints relative, I used app.UseSwaggerForOcelotUI(opt =>
{
opt.DownstreamSwaggerEndPointBasePath = "../swagger/docs";
}); |
Thank you @eymentopcuoglu. It works for me. |
Hello,
I have an issue with the library. The example value of the response of a service is seen differently on the gateway swagger. Let me give an example:
This is the JSON of the response of my endpoint (taken from the service's swagger):
And this is the JSON from the gateway for the same service:
I can't see the node:
What do you think about the problem ?
The text was updated successfully, but these errors were encountered: