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

Support chained package Name for generated python code #8955

Closed
wants to merge 1 commit into from

Conversation

houdejun214
Copy link

@houdejun214 houdejun214 commented Nov 29, 2018

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 and ./bin/security/{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\.
  • Filed the PR against the correct branch: 3.0.0 branch for changes related to OpenAPI spec 3.0. Default: master.
  • Copied the technical committee to review the pull request if your PR is targeting a particular programming language.

Description of the PR

This PR is try to support chained package Name when generate python code,

For example:

if Set with this properties-DpackageName=mycompany_package_name.swagger_clientwhen generate python code.

The api will be generated in a properly folder mycompany_package_name/swagger_client but the support file is not support in this package format

@houdejun214 houdejun214 changed the title Support chained package Name Support chained package Name for generated python code Nov 29, 2018
@houdejun214
Copy link
Author

@kenjones-cisco

@kenjones-cisco
Copy link
Contributor

Thanks @houdejun214 for the PR!
LGTM!
@wing328

@jasiek
Copy link

jasiek commented Aug 20, 2020

What happened?

Was another fix merged in?

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 this pull request may close these issues.

3 participants