Skip to content

add test for paging while overriding api version#387

Merged
iscai-msft merged 3 commits intomainfrom
paging_api_version
Jun 21, 2022
Merged

add test for paging while overriding api version#387
iscai-msft merged 3 commits intomainfrom
paging_api_version

Conversation

@iscai-msft
Copy link
Contributor

If the client has an api version, we want to 1. append that api version to the next link if it doesn't exist OR 2. override the returned api version with that api version.

This test tests that we overide the returned api version in the next link, while preserving the other query parameter returned in the next link

@deyaaeldeen
Copy link
Member

If the client sends the initial request with the right API version, shouldn't the service respond with a next link where the exact API version is appended? Is there a reason for the service not to?

@iscai-msft
Copy link
Contributor Author

@deyaaeldeen the REST behavior here has been not consistent (and the language sdk behaviors have not been consistent either). After talking with @JeffreyRichter , we want to always attach the api version of the client onto these paging calls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants