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
In 3.0.x the instances of the Configuration Python class generated still share the api_key. This has been fixed in 2.4: swagger-api/swagger-codegen#9117
Steps to reproduce
I confirmed that, after creating 2 instances of Configuration changing the content of the api_key dict on one instance changes its content in the other:
>>> from my_client import Configuration
>>> c1 = Configuration()
>>> c1.api_key['Authorization'] = "c1 auth"
>>> c2 = Configuration()
>>> c2.api_key['Authorization'] = "c2 auth"
>>> for c in [c1, c2]:
... print(c.api_key)
...
{'Authorization': 'c2 auth'}
{'Authorization': 'c2 auth'}
Description
Swagger-codegen version
3.0.22
In 3.0.x the instances of the
Configuration
Python class generated still share theapi_key
. This has been fixed in 2.4: swagger-api/swagger-codegen#9117Steps to reproduce
I confirmed that, after creating 2 instances of
Configuration
changing the content of theapi_key
dict on one instance changes its content in the other:Related issues/PRs
swagger-api/swagger-codegen#9117
Suggest a fix/enhancement
The fix for swagger-api/swagger-codegen#9117 (swagger-api/swagger-codegen#9130) could conceivably be ported to
3.0.0
.The text was updated successfully, but these errors were encountered: