Allow continuation token specification in in memory repository #519
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Reduces the restrictions on the use of continuation token specification in the in memory repository by only throwing a not-implemented exception if a continuation token is populated.
At present this will throw if continuation tokens are enabled at all, which makes it impossible to use the in memory repository for integration testing if you're making use of the ContinuationTokenSpecification. This change makes this possible, without having to implement continuation token paging in the in memory repository.
@IEvangelist My team and I are making use of this awesome library but are currently blocked from adding test coverage for our paged endpoints. Please let me know if this change is something you'd be happy with.