Pagination fails after the 160th entry

Open
#7 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api

Research direction

No file or test is named. Start by inspecting the Python library's existing pagination implementation and reproduce a query with more than 160 notices; done means page queries can retrieve results beyond the 160-entry limit, with coverage for later pages if the project has relevant tests.

Written by the indexing model from the issue text.

Description

The API only retrieves 160 entries maximum, forcing me to refine search settings to retrieve more than 160 notices.

Since there is already a pagination feature, it would be best to have a maximum of 160 results per page and then use the page-query to retrieve further data.

This seems to be an issue with the API at large and not with the python library

Dominant language
Python
Stars
16
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bundesAPI/interpol-api

All issues in bundesAPI/interpol-api

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.