refactor(client)!: switch query params objects to use QueryParams
#64
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.
feat(client): add methods for removing additional properties
chore(internal): remove unnecessary validation methods
chore(internal): swap params body getters to use optionals
chore(internal): remove unnecessary nullable annotations
style(internal): minor changes to code ordering and syntax
Migration
If you were accessing
_additionalProperties()
on a query params object, then previously it returnedMap<String, List<String>>
. Now it returns a dedicatedQueryParams
object. TheQueryParams
class is better suited for mapping a key to multiple values and has similar methods toMap
.