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

Define Default Size for extension-requests API to Prevent Returning All Data #2338

Open
6 of 10 tasks
AnujChhikara opened this issue Jan 6, 2025 · 0 comments
Open
6 of 10 tasks

Comments

@AnujChhikara
Copy link
Contributor

AnujChhikara commented Jan 6, 2025

Issue Description

The get extension-requests API currently lacks a default page size. When the size query parameter is not provided, the API returns all available data. This can lead to performance issues, especially when the dataset is large. To improve the usability and efficiency of the API, a default page size should be implemented.

Expected Behavior

  • Define a default page size for the get extension-requests API (e.g., 20 records per page).

Current Behavior

  • When the size query parameter is not provided , the API returns all available records instead of limiting the number of records.

Screenshots

Reproducibility

  • This issue is reproducible
  • This issue is not reproducible

Steps to Reproduce

  • Send a GET request to the extension-requests API endpoint without the size query parameter. extension-requests
  • See it is returning over 1k response if we not provide size query param

Severity/Priority

  • Critical
  • High
  • Medium
  • Low

Additional Information

Checklist

  • I have read and followed the project's code of conduct.
  • I have searched for similar issues before creating this one.
  • I have provided all the necessary information to understand and reproduce the issue.
  • I am willing to contribute to the resolution of this issue.
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

No branches or pull requests

1 participant