Created by: ccouzens
PR checklist
-
Read the contribution guidelines. -
Ran the shell script under ./bin/
to update Petstore sample so that CIs can verify the change. (For instance, only need to run./bin/{LANG}-petstore.sh
,./bin/openapi3/{LANG}-petstore.sh
if updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in.\bin\windows\
. If contributing template-only or documentation-only changes which will change sample output, be sure to build the project first. -
Filed the PR against the correct branch: master
,4.1.x
,5.0.x
. Default:master
. -
Copied the technical committee to review the pull request if your PR is targeting a particular programming language. No- I don't think this is going to be the accepted solution, so I won't get their attention at this point.
Description of the PR
Add an option x-allow-dynamic-resource
to tell path parameters not to encode slashes (/
). This provides a route for backwards compatibility for people who rely on slashes not being encoded.
I've only done this for Ruby-client.
The 1st commit is where I change the sample YAML and add the route. The 2nd commit is when I add the extension to Ruby.
https://github.com/OpenAPITools/openapi-generator/issues/3119