-
Notifications
You must be signed in to change notification settings - Fork 591
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
Need types for the paginator start token #1882
Comments
+1 |
Greetings! We’re closing this issue because it has been open a long time and hasn’t been updated in a while and may not be getting the attention it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to comment or open a new issue. |
Greetings! We’re closing this issue because it has been open a long time and hasn’t been updated in a while and may not be getting the attention it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to comment or open a new issue. |
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. |
Is your feature request related to a problem? Please describe.
Currently the paginators start token is
any
type. It can be more specific to individual paginators. For example inpaginateScan()
's start token is the type ofExclusiveStartKey
. We can use generic to make the pagiator configuration interface include the start token type.Without this type, users will be confused if they have an existing
ExclusiveStartKey
, where should they use. Take #1864 (comment) for example.Describe the solution you'd like
PaginationConfiguration
interface can contain a generic like:In individual paginator, the function signature can be:
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
/cc @alexforsyth
The text was updated successfully, but these errors were encountered: