Currently, the configuration includes defaultProvider and defaultRegion. However, the overloaded methods in *Factory allow users to manually specify the provider and region in the method's signature. This means that default values can be specified in the configuration, while overloading methods render them useless. The existence of multiple overloaded methods makes it difficult for developers to grasp the underlying logic and which heuristics are applied if different methods are called.
To resolve this, I propose adding two fields to the configuration: java String forcedProvider; and java String forcedRegion. This will clarify what happens if these parameters are supplied and allow the removal of overloaded methods. However, it will require a new version, breaking the API with old calls.
Currently, the configuration includes defaultProvider and defaultRegion. However, the overloaded methods in *Factory allow users to manually specify the provider and region in the method's signature. This means that default values can be specified in the configuration, while overloading methods render them useless. The existence of multiple overloaded methods makes it difficult for developers to grasp the underlying logic and which heuristics are applied if different methods are called.
To resolve this, I propose adding two fields to the configuration:
java String forcedProvider;andjava String forcedRegion. This will clarify what happens if these parameters are supplied and allow the removal of overloaded methods. However, it will require a new version, breaking the API with old calls.