feat(api): add pagination support to IMAP scan history endpoint#247
Merged
Userunknown84 merged 1 commit intoJun 24, 2026
Merged
Conversation
|
@devprashant19 is attempting to deploy a commit to the Aditya Sharma's projects Team on Vercel. A member of the Team first needs to authorize it. |
Userunknown84
approved these changes
Jun 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR implements pagination for the IMAP scan history endpoint. Previously, the API fetched historical scan data using a hardcoded
limit=100, making any scans beyond the most recent 100 permanently inaccessible to the user via the UI.Changes
backend/email_connectors/imap_store.py: Updatedget_scan_historyto accept anoffsetparameter and updated the underlying SQLite query to includeOFFSET ?.backend/api.py: Updated the/imap/scan-resultsroute to parse an optionalpagequery parameter (defaulting to 1). The endpoint calculates the correct offset and passes it down to the database layer, returning the paginated results along with the current page metadata.Related Issues
Type of Change
Pre-submission Checklist
pagequery parameter successfully fetches subsequent segments of history.pageis omitted.