-
Notifications
You must be signed in to change notification settings - Fork 578
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
feat(types): add pagination stopOnSameToken option #3524
Conversation
@kuhe It looks good. Because this change also updates the generated client's code, can you re-generate the clients? Regarding the CodeBuild failure, you need to merge the upstream PR before restart the CodeBuild. |
300fed9
to
baff6f1
Compare
@AllanZhengYP thanks for the doc update. I've pushed the client changes. Something I'd like to PR in the future is a |
@kuhe I like the idea of more abstractions. Though I have some questions with the function input. Can you follow up on this in a separate issue / internal doc? |
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.
Approve it, please regenerate the paginators after today's release before merging it.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread. |
Issue
#3490
Description
Add an option to stop paginators on receiving the same token (indicates tail has been reached).
Testing
tested in the smithy change
Additional context