Conversation
|
Could we avoid renaming the public API? I understand it would make things more clear and direct but a lot of clients already support the V0 API and there's no value for us to apply a breaking change on the v0 api as it is not being updated anymore.
Doesn't feel like that's really worth losing the compatibility for older clients. |
|
Right, my bad. |
|
Almost every breaking change is reverted. The only breaking change is Adding the latter or removing the former would be breaking nonetheless (as Go does not support optional parameters or function overloading), so the parameter is replaced. |
|
It has been tested with |
|
Since Go does not support optional parameters, many legacy function parameters in here will be left unused. Feel free to let me know if you want for these function parameters to be removed as well. |
|
Most breaking changes reverted. |
|
Closed in anticipation of a major update that adds v1 support but deletes all v0 features. |
The following pull request is a toned down version of #12. This pull request focuses solely on the changes done to the SDK in the v0 of the API. Such as:
LICENSE.goversion to 1.21 to be able to use theminfunction.