Miňo Martiniak

Hi, Are the properties in the original downstream documentation?

Hi, please can you attach origin OpenApi schema definition of address type? _(you've probably attached an example from swagger ui)_ thanks.

Hi, it appears that indirectly referenced types are not included in the resulting scheme. I will try fix it next week.

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

Hi, Thanks. Contributing is welcome.

Hi, thanks for your issue. Yes, unfortunately now this project support only `{everything}` as wildcard. I plan implemented this feature, but after issue #56. I don't have as much time...

Hi @dgustala, in this case `{companyId}` is not "wildcard", but a path parameter. If the same parameter at the same position exists in the downstream path, the documentation can be...

Hi, thanks for the report. Problem is that your downstream service documentation doesn't contains paths like `/api/application/95/tasks`. This package unfortunately doesn't support parameter translating beetwen upstream and downstream path template....

Hi @DaleyKD Thanks for your issue. Your use case looks different. @ondrix try to used constant value `95` instead of route parameter `{something}`. Your scenario can work. [See my example.](https://github.com/Burgyn/Sample.OcelotWithRoutingParameters)

Hi @jwillmer, I have had a similar idea in my head since the beginning of this project (#34). Unfortunately, I never really needed it so much that I would realize...