-
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
Pagination operation should specify type for its third parameter #1668
Comments
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.
The pagination operation currently accepts
any
for its third parameter. For example:aws-sdk-js-v3/clients/client-dynamodb/pagination/ListTablesPaginator.ts
Lines 23 to 27 in 07ac6be
The type for the third parameter is known in advance. For example, it's
__HttpHandlerOptions
aws-sdk-js-v3/clients/client-dynamodb/DynamoDB.ts
Line 1207 in 07ac6be
This is a problem, as it:
...args
in command instead of send operation #1665Describe the solution you'd like
The type for the third parameter in pagination should be defined. For example:
Describe alternatives you've considered
Sticking with the lack of types for third parameter in pagination.
The text was updated successfully, but these errors were encountered: