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.

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

Closed
trivikr opened this issue Nov 9, 2020 · 3 comments
Closed

Pagination operation should specify type for its third parameter #1668

trivikr opened this issue Nov 9, 2020 · 3 comments
Labels
feature-request New feature or enhancement. May require GitHub community feedback. p3 This is a minor priority issue queued This issues is on the AWS team's backlog

Comments

@trivikr
Copy link
Member

trivikr commented Nov 9, 2020

Is your feature request related to a problem? Please describe.
The pagination operation currently accepts any for its third parameter. For example:

export async function* listTablesPaginate(
config: DynamoDBPaginationConfiguration,
input: ListTablesCommandInput,
...additionalArguments: any
): Paginator<ListTablesCommandOutput> {

The type for the third parameter is known in advance. For example, it's __HttpHandlerOptions

public listTables(args: ListTablesCommandInput, options?: __HttpHandlerOptions): Promise<ListTablesCommandOutput>;

This is a problem, as it:

Describe the solution you'd like
The type for the third parameter in pagination should be defined. For example:

export async function* listTablesPaginate(
  config: DynamoDBPaginationConfiguration,
  input: ListTablesCommandInput,
  options?: __HttpHandlerOptions
): Paginator<ListTablesCommandOutput> {

Describe alternatives you've considered
Sticking with the lack of types for third parameter in pagination.

@trivikr trivikr added the feature-request New feature or enhancement. May require GitHub community feedback. label Nov 9, 2020
@trivikr trivikr changed the title Pagination operation should specify types for it's third parameter Pagination operation should specify type for it's third parameter Nov 9, 2020
@trivikr trivikr changed the title Pagination operation should specify type for it's third parameter Pagination operation should specify type for its third parameter Nov 9, 2020
@github-actions
Copy link

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.

@github-actions github-actions bot added the closing-soon This issue will automatically close in 4 days unless further comments are made. label Nov 10, 2021
@trivikr trivikr removed the closing-soon This issue will automatically close in 4 days unless further comments are made. label Nov 10, 2021
@github-actions
Copy link

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.

@github-actions github-actions bot added the closing-soon This issue will automatically close in 4 days unless further comments are made. label Nov 11, 2022
@trivikr trivikr removed the closing-soon This issue will automatically close in 4 days unless further comments are made. label Nov 11, 2022
@RanVaknin RanVaknin added the p2 This is a standard priority issue label Mar 7, 2023
@RanVaknin RanVaknin added p3 This is a minor priority issue queued This issues is on the AWS team's backlog and removed p2 This is a standard priority issue labels Feb 28, 2024
@aBurmeseDev aBurmeseDev closed this as not planned Won't fix, can't repro, duplicate, stale Jun 19, 2024
Copy link

github-actions bot commented Jul 4, 2024

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request New feature or enhancement. May require GitHub community feedback. p3 This is a minor priority issue queued This issues is on the AWS team's backlog
Projects
None yet
Development

No branches or pull requests

3 participants