Skip to content

feat(158): add guidance on page token validity #286

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

toumorokoshi
Copy link
Member

Currently, the AEPs do not include guidance on a complex nuance of page tokens, when they may not be able to properly continue a request. Documenting that guidance is helpful.

Fixes #189

🍱 Types of changes

What types of changes does your code introduce to AEP? Put an x in the boxes
that apply

  • Enhancement
  • New proposal
  • Migrated from google.aip.dev
  • Chore / Quick Fix

📋 Your checklist for this pull request

Please review the AEP Style and Guidance for
contributing to this repository.

General

💝 Thank you!

Currently, the AEPs do not include guidance on a complex 
nuance of page tokens, when they may not be able to properly
continue a request. Documenting that guidance is helpful.

Fixes aep-dev#189
@toumorokoshi toumorokoshi requested a review from a team as a code owner March 20, 2025 04:01
@toumorokoshi toumorokoshi requested a review from mkistler March 20, 2025 04:01
@toumorokoshi
Copy link
Member Author

@mkistler would you mind taking a look? I think the suggestion around documenting page token validity was from you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

pagination: consider re-adding guidance on pagination token
1 participant