Feature/support continuation token limit property

[victormarante]

This PR will add support for the Cosmos SDK API QueryOptionsClass which enables consumers of these APIs to provide their own settings for the CosmosClient.

This PR aims to solve: #432

@IEvangelist I have made an initial PR here (no tests or so yet) in order to make sure I am on the right track before spending more time on this. I have two questions that will need discussion:

• It might be confusing for users to provide both the query options AND page size, as they might enter the same information twice (if they provided MaxItemCount in query options to begin with). I do not know what your thought is about this.
• Are you ok with the method overloading (i.e. that I simply call the new method from the existing API), with same logic + a default instance of QueryOptionsClass

Tasks

• Write tests
• Add default values for new API to protect user from un-wanted side-effects

[IEvangelist]

Looks okay thus far... Looks like some of these are new APIs and one is modified (PageAsync). This is a breaking change, it's probably better to add all new APIs.

[victormarante]

Looks okay thus far... Looks like some of these are new APIs and one is modified (PageAsync). This is a breaking change, it's probably better to add all new APIs.

Not entirely sure what you mean by this. Looking at the code, I have added 4 new methods to the IReadOnlyRepository, where in each case the existing functions simply call the new overloads with a default QueryRequestOptions (either passing nothing or the MaxItemCount, as this was previously configured).

EDIT: Or are you referring to the fact that I have moved the logic to the new APIs, and let the existing APIs call the new overloads with a default QueryRequestOptions? I think this will have no impact as this already happens under the hood (to my understanding).

[IEvangelist]

Ok, sounds good. When I was first looking at this, it wasn't clicking that those were the changes. That makes sense, and that's what I was hoping for. This is good!

[IEvangelist]

@all-contributors please add @victormarante for code

[allcontributors]

@IEvangelist

@victormarante already contributed before to code

[victormarante]

Hi, great, thanks for reviewing this far. I would like to add some tests but unsure what exactly you prefer in terms of tests?

[IEvangelist]

Hi, great, thanks for reviewing this far. I would like to add some tests but unsure what exactly you prefer in terms of tests?

There are a lot of tests that already exist, rely on those for inspiration for new tests.

[mateuszkumpf]

You must expect that null could be passed. Initialize requestOptions if the value is null.

[mateuszkumpf]

Or throw exception

[IEvangelist]

But the requestOptions isn't nullable, are you implying that we should protect against it anyway?

[mateuszkumpf]

By default, I don't trust users 😂 But if for you it's ok then for me too 😄