Introduce faster and richer way to add objects as query parameters #1974
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.
Description
This PR is a result of the discussion in PR#1897. It introduces a new way of adding objects as query parameters to a RestRequest instance when the object type is known beforehand, which allows for a lot of optimizations to be made.
Apart from this, this PR also builds on top of pre-existing functionality, allowing for things like:
IEnumerable
types.IEnumerable
property.IConvertible
,IEnumerable
orIFormattable
, use the type's definedTypeConverter
and delegate conversion to string to it instead of using.ToString()
. This allows users to create custom converters to determine how certain types should be stringified. If no custom converter is defined, we will fall back to.ToString()
anyways.AddObject
implementation.Purpose
This pull request is a:
Checklist