-
Notifications
You must be signed in to change notification settings - Fork 94
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
Aggregation schema not full #191
Comments
Hi, Are the properties in the original downstream documentation? |
Hi! Ocelot config: Original Json-Model for accountMe: |
Hi, please can you attach origin OpenApi schema definition of address type? (you've probably attached an example from swagger ui) thanks. |
originJson.zip thanks. |
Hi, it appears that indirectly referenced types are not included in the resulting scheme. I will try fix it next week. |
thanks! |
After much research, I found that it is not easy to add such an indirect reference to the resulting scheme. Implementing of this requirement would require several days of work. I'm sorry, but I don't have time for this right now. However, I'm open for PR. |
We will wait for this change in the future. Thanks! |
Hi, Thanks. Contributing is welcome. |
I use custom aggregation with two routes. First route have simple model and schema is ok. But second model is very big and have many object-properties in it. This Object-properties is not load in output schema and this objects appear as null. For example, profile has list of addresses. And model of address can not been appeared in schema.
"Aggregates": [ { "RouteKeys": [ "accountV1Settings", "accountV1Me" ], "Description": "Account descriptions", "UpstreamPathTemplate": "/gw/api/acc" } ],
The text was updated successfully, but these errors were encountered: