Skip to content

ListRequestOptions should know how to compose it's own querystring #91

@Psypher9

Description

@Psypher9

Is your feature request related to a problem? Please describe.
Currently when using ListRequestOptions, our pattern is to use a bunch of repetitive code to set the query params for each individual request, over and over ad nauseum. Example:

image

This happens over and over, but we use the same ListRequestOptions, so all options are already held internally.

Describe the solution you'd like
Instead of being repetitive, we should build the ListRequestOptions in such a way that it knows how to build it's own query string and that string is then appended to the request URI.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requesthelp wantedExtra attention is needed

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions