We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Using this issue to describe the changes, but will spin-off individual issues for each:
top
maxpagesize
results_per_page
orderBy
CreatedDateTimeUtc asc / desc
For beta 1 we will:
skip
The text was updated successfully, but these errors were encountered:
kristapratico
Successfully merging a pull request may close this issue.
Using this issue to describe the changes, but will spin-off individual issues for each:
top
should now behave liketop
. We will expose atop
parameter mapped to the servicetop
parameter.maxpagesize
added to the pageable methods. We should map ourresults_per_page
kwarg to thisorderBy
parameter added. Currently onlyCreatedDateTimeUtc asc / desc
supported. This might take some design work.For beta 1 we will:
top
/results_per_page
orskip
yet. We don't want the behavior to change on users once the fixes are deployed.The text was updated successfully, but these errors were encountered: