Update generated page response#1139
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1139 +/- ##
============================================
+ Coverage 86.09% 86.09% +<.01%
- Complexity 3618 3687 +69
============================================
Files 364 372 +8
Lines 14264 14544 +280
Branches 1589 1626 +37
============================================
+ Hits 12280 12522 +242
- Misses 1552 1585 +33
- Partials 432 437 +5
Continue to review full report at Codecov.
|
| public static class ListShelvesPagedResponse extends PagedListResponseImpl<ListShelvesRequest, ListShelvesResponse, Shelf> { | ||
| public static class ListShelvesPagedResponse implements PagedListResponse<Shelf> { | ||
|
|
||
| private final PagedListResponseContext<RequestT, ResponseT, ResourceT> context; |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
| } | ||
| } | ||
|
|
||
| public Object getNextPageToken() { |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
garrettjonesgoogle
left a comment
There was a problem hiding this comment.
LGTM after the name issue is fixed, and after you verify tests pass in api-client-staging after regenerating there.
|
|
||
| public abstract String name(); | ||
|
|
||
| public abstract String pageName(); |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
|
Thanks for catching more that I didn't notice - LGTM |
Work in progress, wanted to get feedback on the approach. Each generated paged response object and page object has a lot more methods that before, but the implementations are very simple, with as much work as possible being delegated to the context object.