Created by: ashanbrown
I could use some advice on this one. The fix for https://github.com/OpenAPITools/openapi-generator/issues/51 (PR https://github.com/OpenAPITools/openapi-generator/pull/60) broke our use of the go generator because it now assumes unspecified (i.e. "any-type") schemas will be map[string]interface{} instead of *interface{}. This change tries to restore the empty interface, albeit as interface{} instead of *interface{}. I'm not sure what the intent of using a pointer to an interface was in the original code but maybe that would be preferred . This code does not change the generated petshop code (but maybe petshop should be updated to include an "any-type" schema).
The "any-type" schema is mentioned at https://swagger.io/docs/specification/data-models/data-types/ which claims to be a guide to openapi 3.0, but I don't see it mentioned by name in the "open-api" spec.
Thanks for your help and for keeping this project moving forward.
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.shand./bin/security/{LANG}-petstore.shif 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\. -
Filed the PR against the correct branch: master,3.3.x,4.0.x. Default:master. -
Copied the technical committee to review the pull request if your PR is targeting a particular programming language.
Description of the PR
(details of the change, additional tests that have been done, reference to the issue for tracking, etc)