`SantanderApiClient` receives a configuration class, raising the complexity level to use

[avelino]

client = SantanderApiClient(SantanderClientConfiguration(
  client_id="client_id",
  client_secret="client_pk",
  cert="certificate_path",
  base_url="api_url",
  workspace_id="optional"
))

I understand why we're using a class for client configuration, but this raises the complexity level to use the SDK.
The ideal for an open source project is to be simple and not make the user think too much, e.g.

Need to integrate with XXX, how do I do it? client = ClientClass(... params)

Internally we can use the configuration class, but we shouldn't outsource this to the user.

proposal

client = SantanderApiClient(
  client_id="client_id",
  client_secret="client_pk",
  cert="certificate_path",
  base_url="api_url",
  workspace_id="optional"
)

[darkdks]

You are right. This class (SantanderClientConfiguration) is already planned to be removed along with the refactoring of the Santander flow abstraction to also handle barcode payments. Previously, when it was internal code for one system, this class had many other responsibilities and behaved differently. Today, it has become a data class, which no longer makes sense.

Thank you for opening the issue. =)