You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In latest versions of swagger-client we've utilized the spec compliant OpenAPI Path template parsing.
Here is what OpenAPI stipulates about path templating:
Path templating refers to the usage of template expressions, delimited by curly braces ({}), to mark a section of a URL path as replaceable using path parameters. link
This specifies that path template forms a relative URL reference. This is what OpenAPI stipulates about relative URL reference:
Unless specified otherwise, all properties that are URLs MAY be relative references as defined by RFC3986link
This means that parsing of path template MUST be RFC3986 compliant and thus cannot contain unencoded empty string values. As the path template with empty space doesn't qualify as valid path template, it's not being resolved.
Having said that, we didn't introduce a regression, we fixed a bug that allowed to define path templates as invalid RFC3986. Now we don't allow it anymore.
To remedy specific situation as described in the description of this issue
Q&A (please complete the following information)
Content & configuration
Describe the bug you're encountering
If the URL has spaces, then the path parameters are not resolved correctly.
To reproduce...
Steps to reproduce the behavior:
Current behavior
Expected behavior
Resolved req should be -
Screenshots
Additional context or thoughts
The text was updated successfully, but these errors were encountered: