API request usability and stability improvements #202
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The APIClient system forms the foundation for most everything within the Client SDK, and as such the types and handling of data sent using these classes and protocols is of the utmost importance. To that end, this PR introduces several enhancements that will improve APIClient for future changes.
APIRequestArgument
instead ofAny
to improve how arguments are handled, tested, and validated.APIRequestArgument
conformances to several key types, includingJWT
,GrantType
, andToken.Kind
.APIRequestArgument
value conversion for types that already conform toRawRepresentable
with aString
value type.SDKVersion.register
is thread-safe, and begin initial adoption of theSendable
protocol.