Sizes of cursors and pages are integers in REST. #3938
Merged
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.
Summary
This change addresses the problem of uint64 not being representable in javascript, leading to a swagger definition of two numbers related to cursors, namely
size
andtotal_records
, having string type rather than integer. Using a uint32 generates the desired type and is sufficient for paging purposes.This is a breaking change, which is why this commit contains changes to CLI as well. For the record, the feature is currently under feature flag.
Fixes #3934
Change Type
Mark the type of change your PR introduces:
Testing
Manual and unit tests.
Review Checklist: