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

Endpoint shows in dropdown but it's content is not loaded #59

Open
ondrix opened this issue Dec 9, 2019 · 4 comments
Open

Endpoint shows in dropdown but it's content is not loaded #59

ondrix opened this issue Dec 9, 2019 · 4 comments
Assignees
Labels
enhancement New feature or request low priority ⬇️ I'm not planning on it.
Milestone

Comments

@ondrix
Copy link

ondrix commented Dec 9, 2019

One of my serivces does not show swagger doc. Other looks fine but this one loads into dropdown but swagger doc does not load

To Reproduce
If it is a possible attache:

  1. Original downstream swagger.json.
  2. Ocelot ReRoutes configuration.
    ocelot.zip
@Burgyn Burgyn added this to the Version 2.0 milestone Dec 9, 2019
@Burgyn Burgyn added the enhancement New feature or request label Dec 9, 2019
@Burgyn
Copy link
Owner

Burgyn commented Dec 9, 2019

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.

I will support it when I finish issue #56.

@Burgyn Burgyn modified the milestones: Version 2.0, Version 2.1.0 May 27, 2020
@DaleyKD
Copy link

DaleyKD commented Jul 27, 2020

Thanks so much for taking the time on this package. Any idea on a timeline for this? We have routes like this:

{
    "DownstreamPathTemplate": "/{accountId}/api/{everything}",
    "DownstreamScheme": "http",
    "ServiceName": "account-api",
    "UpstreamPathTemplate": "/{accountId}/api/a/{everything}",
    "UpstreamHttpMethod": [],
}

and can't use this package until this issue is resolved.

Thanks again.

@Burgyn
Copy link
Owner

Burgyn commented Jul 28, 2020

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.

@DaleyKD
Copy link

DaleyKD commented Jul 28, 2020

@Burgyn : Thanks, man. I totally missed that.

While we may not use this in a production scenario for our needs, it does seem like it'll be VERY good for local development.

Thank you VERY much for your effort on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request low priority ⬇️ I'm not planning on it.
Projects
None yet
Development

No branches or pull requests

3 participants