Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[request]: Add support for pagination/streaming #508

Closed
jmklix opened this issue Apr 6, 2022 Discussed in #105 · 2 comments
Closed

[request]: Add support for pagination/streaming #508

jmklix opened this issue Apr 6, 2022 Discussed in #105 · 2 comments
Labels
feature-request A feature should be added or improved.

Comments

@jmklix
Copy link
Member

jmklix commented Apr 6, 2022

Discussed in #105

Originally posted by geekingfrog June 10, 2021
There are many requests in many services which returns paginated responses. For example, ListObject or ListBuckets in S3, Scan in DDB and so on.

It would be really nice to have a unified way to provide a method which returns a futures::stream, or I guess, a TryStream since the items are likely to be Results.

Yes absolutely! We have an RFC design for paginators, would love your thoughts: smithy-lang/smithy-rs#346
@jmklix jmklix added the feature-request A feature should be added or improved. label Apr 6, 2022
@jdisanti
Copy link
Contributor

jdisanti commented Apr 7, 2022

Paginators have already been implemented.

@jdisanti jdisanti closed this as completed Apr 7, 2022
@github-actions
Copy link

github-actions bot commented Apr 7, 2022

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature-request A feature should be added or improved.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jdisanti @jmklix