Skip to content

Conversation

mgu
Copy link
Contributor

@mgu mgu commented Jul 16, 2021

Description
We have a usecase where we need two Adyen clients using two different
versions in the same code base.

Overriding version using settings.API_xxx_VERSION does not allow us to use
multiple API versions depending on our usecases.

Adding the possibility to override the API versions in the Client
constructor solves this issue

Tested scenarios
don't change settings.API_xxx_VERSION but pass version using kwargs when instanciating Adyen object

Fixed issue:

We have a usecase where we need two Adyen clients using two different
versions in the same code base.
Overriding version using settings.xxx_VERSION does not allow us to use
multiple API versions depending on our usecases.

Adding the possibility to override the API versions in the Client
constructor solves this issue
@mgu
Copy link
Contributor Author

mgu commented Jul 16, 2021

there was no test related to settings but I can add one if necessary

@mgu
Copy link
Contributor Author

mgu commented Sep 6, 2021

should I close my PR ?

@acampos1916
Copy link
Contributor

Sorry for the unresponsiveness @mgu.

What do you think of this suggestion @AlexandrosMor @Aleffio ?

@AlexandrosMor AlexandrosMor merged commit a6f4bc6 into Adyen:develop Sep 7, 2021
@mgu mgu deleted the feat/override-versions-at-init branch September 7, 2021 11:50
@AlexandrosMor AlexandrosMor mentioned this pull request Oct 18, 2021
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