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

Add possibility of defining a "prefix" for the API path #24

Closed
maticardenas opened this issue Mar 12, 2024 · 0 comments · Fixed by #25
Closed

Add possibility of defining a "prefix" for the API path #24

maticardenas opened this issue Mar 12, 2024 · 0 comments · Fixed by #25
Assignees

Comments

@maticardenas
Copy link
Owner

When defining an OpenAPI specification, the correct and expected way is to not include any path within the servers URLs (https://example.com).

However, it could be the case that old APIs have already defined a server URL that way (https://example.com/api/v1/pets/tasks/), or maybe the fact that a very long common same path exists makes it easier to define it in the server URL, leaving to shorter and clearer paths in the endpoints themselves.

Given that the package currently ignores the server URL, the fact of not retrieving the necessary prefix from this server URL will make the tests to fail given the path won't be found.
A prefix functionality could be introduced, in order to handle these scenarios.

@maticardenas maticardenas self-assigned this Mar 12, 2024
@maticardenas maticardenas linked a pull request Mar 12, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant