API: New pagination endpoint for applications#6552
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #6552 +/- ##
===========================================
- Coverage 63.39% 47.69% -15.71%
===========================================
Files 484 645 +161
Lines 67624 87949 +20325
===========================================
- Hits 42869 41943 -926
- Misses 21065 43251 +22186
+ Partials 3690 2755 -935
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
…e creator but has no local state. This handling is consistent with how assets are handled.
Co-authored-by: Pavel Zbitskiy <65323360+algorandskiy@users.noreply.github.com>
…ations of parameters when not needed.
algorandskiy
left a comment
There was a problem hiding this comment.
Approved, I still prefer include=params vs include-params=true tho.
…tual applications for the associated account.
… Omit the deleted field if an app is not marked deleted.
… sparse test ids.
…more aligned with the 'include' param on the accounts endpoint.
jannotti
left a comment
There was a problem hiding this comment.
I'm ok as is. but I did make one more comment that it could be nice to segregate "params" into different things that could be included.
Summary
Introduces a new pagination endpoint for an account's applications.
Further addresses #6533 with a more scalable solution.
Test Plan
Handlers tests were enhanced to exercise the new endpoint and various validation checks.