-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[schema] #2108: Add pagination #2107
[schema] #2108: Add pagination #2107
Conversation
2e1058d
to
f53b086
Compare
95f6577
to
b8438b1
Compare
b8438b1
to
332c936
Compare
332c936
to
7a68b29
Compare
7a68b29
to
eb19963
Compare
) -> Result<Scale<VersionedQueryResult>, warp::http::Response<warp::hyper::Body>> { | ||
) -> Result<Scale<VersionedPaginatedQueryResult>, warp::http::Response<warp::hyper::Body>> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The strange thing is that Client
still expects a VersionedQueryResult
in request_with_pagination
, but seems to successfully decode a query result that is actually a VersionedPaginatedQueryResult
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BTW maybe this PR should be categorized as [schema]
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not PR, but commit. If you try to add schema
to the PR title, it will not pass CI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The strange thing is that Client still expects a VersionedQueryResult in request_with_pagination, but seems to successfully decode a query result that is actually a VersionedPaginatedQueryResult
I'm guessing that it tries to decode the subset that is a VersionedQueryResult
, but it should be updated. Good catch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not PR, but commit. If you try to add
schema
to the PR title, it will not pass CI.
Timely, #2115 shows an exception
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, later I can resolve the appearance discrepancy between VersionedPaginatedQueryResult
and VersionedQueryResult
eb19963
to
cf31d89
Compare
Signed-off-by: BAStos525 <[email protected]>
Signed-off-by: Aleksandr Petrosyan <[email protected]>
cf31d89
to
1a1a835
Compare
Signed-off-by: Aleksandr Petrosyan <[email protected]>
1a1a835
to
fa7dd77
Compare
Signed-off-by: Aleksandr Petrosyan <[email protected]>
Signed-off-by: Aleksandr Petrosyan <[email protected]>
Signed-off-by: Aleksandr Petrosyan <[email protected]>
Signed-off-by: Aleksandr Petrosyan <[email protected]>
Signed-off-by: Aleksandr Petrosyan <[email protected]>
Signed-off-by: BAStos525 [email protected]
Description of the Change
Add pagination support for SDKs.
Issue
Closes #2108
Benefits
Pagination added to queries, so that SDKs have access to the Pagination struct.