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
[Optional] Sponsorship to speed up the bug fix or feature request (example)
Description
If you're dropping OpenAPI into python project you may decide to leverage pythonSrcRoot to have the generated code conform to your existing folder structure. The problem, though, is since the generated code doesn't know the true module root, the imports become a pain and don't work well. We need to introduce the ability to include the pythonSrcRoot into the import namespace.
openapi-generator version
5.1.1
Related issues/PRs
Suggest a fix
The fix here would be to introduce a new generator config value that would allow users to specify they want the pythonSrcRoot included in Imports then have the generator modify packageName accordingly.
The text was updated successfully, but these errors were encountered:
Bug Report Checklist
Description
If you're dropping OpenAPI into python project you may decide to leverage
pythonSrcRoot
to have the generated code conform to your existing folder structure. The problem, though, is since the generated code doesn't know the true module root, the imports become a pain and don't work well. We need to introduce the ability to include thepythonSrcRoot
into the import namespace.openapi-generator version
5.1.1
Related issues/PRs
Suggest a fix
The fix here would be to introduce a new generator config value that would allow users to specify they want the
pythonSrcRoot
included in Imports then have the generator modifypackageName
accordingly.The text was updated successfully, but these errors were encountered: