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.

Sign up for GitHub

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

Jump to bottom

BasePath doesn't get properly returned within SwaggerUI Middleware #1834

Open
nielsbox opened this issue Dec 11, 2023 · 0 comments · May be fixed by #1835
Open

BasePath doesn't get properly returned within SwaggerUI Middleware #1834

nielsbox opened this issue Dec 11, 2023 · 0 comments · May be fixed by #1835

Comments

@nielsbox
Copy link
Collaborator

nielsbox commented Dec 11, 2023 •
edited

Description

When using a Swagger spec with a basePath set to / and then fetching the specification via the Swagger UI middleware, the basePath returned is set to `` (empty string). Which is invalid Swagger 2.0, you can check yourself by validating contract that within connexion. Specification.from_dict

Expected behaviour

The basePath stays /

Actual behaviour

The basePath is empty

Steps to reproduce

Use a Swagger 2.0 spec with a / as basePath, then fetch the spec from the Swagger UI middleware

Additional info:

Output of the commands:

  • python --version 3.10
  • pip show connexion | grep "^Version\:" 3.0.5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Handle Swagger slash basepath within Swagger UI Middleware spec-first/connexion
1 participant
@nielsbox