We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
if we have a openapi 3.0 specification like this:
servers: - url: https://api.example.com/{basePath} description: Production server (uses live data) variables: basePath: default: "v1/path-a/path-b/pathC
It will report error that the basePath doesn't match the pattern "[^\/#\?]+?"
basePath
This pattern check comes from the package path-to-regexp.
path-to-regexp
But I don't think we need such constrains. There is no such limitation in OpenAPI 3 specification
According to https://swagger.io/docs/specification/api-host-and-base-path/, it says:
Variables can have arbitrary values, or may be restricted to an enum.
The text was updated successfully, but these errors were encountered:
fix cdimascio#380: allow any string to be servers variables
050001b
b0c2a0c
Successfully merging a pull request may close this issue.
Problem description
if we have a openapi 3.0 specification like this:
It will report error that the
basePath
doesn't match the pattern "[^\/#\?]+?"Discussion
This pattern check comes from the package
path-to-regexp
.But I don't think we need such constrains. There is no such limitation in OpenAPI 3 specification
According to https://swagger.io/docs/specification/api-host-and-base-path/, it says:
The text was updated successfully, but these errors were encountered: