ml-opensource / ml-opensource/API-manifesto
Topic: Pagination
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 10
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
- why it's needed
- Offset versus cursor
- recommended structure
- See: https://slack.engineering/evolving-api-pagination-at-slack-1c1f644f8e12
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no file, test, or documentation entry point. Start by locating where API guidance is maintained, then use the listed topics and the linked Slack article as references; done means the documentation explains why pagination is needed, compares offset and cursor approaches, and recommends a structure.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100