-
Notifications
You must be signed in to change notification settings - Fork 524
API: Revert boxes pagination #6343
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
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #6343 +/- ##
==========================================
+ Coverage 51.90% 51.96% +0.05%
==========================================
Files 653 653
Lines 87469 87460 -9
==========================================
+ Hits 45401 45447 +46
+ Misses 39198 39139 -59
- Partials 2870 2874 +4 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
algorandskiy
left a comment
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.
I reviewed the key files (i.e. excl. tests) and it is LGTM
cce
left a comment
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.
To aid in review, I created a branch with the three PR commits reverted here omitted, using git rebase:
https://github.com/gmalouf/go-algorand/compare/revert-boxes-pagination..cce:go-algorand:rebuild-revert-6343
https://github.com/cce/go-algorand/compare/rebuild-revert-6343..gmalouf:go-algorand:revert-boxes-pagination
(important to use a .. diff instead of a ... diff to avoid including other commits on master not related)
The diff looks good!
Summary
This reverts #6279. Introducing box pagination as done in that PR broke an implicit contract that impacts enough users to warrant a (future) new endpoint:
After additional feedback from users, we are taking the short term step of reverting the existing endpoint enhancements. A future PR may add pagination functionality, on an endpoint/sub-endpoint that does not impact the existing userbase.
Test Plan
Existing tests should all pass.