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

Name conflict between models.Response and types.Response #1081

Open
drwilly opened this issue Jul 22, 2024 · 1 comment
Open

Name conflict between models.Response and types.Response #1081

drwilly opened this issue Jul 22, 2024 · 1 comment

Comments

@drwilly
Copy link

drwilly commented Jul 22, 2024

I ran into an OpenAPI spec which included a Response type. That caused a name conflict in the generated python code:

from ...models.response import Response
from ...types import Response

This was fixed easily enough using a class_overrides config, but since the classes in types.py are pretty generic I think it would be better if the classes were just fully qualified to avoid this kind of conflict.

@lokkju
Copy link

lokkju commented Nov 7, 2024

@drwilly could you add the class_overrides stanza you used here?

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

No branches or pull requests

2 participants