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

Make Pagination Optional #167

Open
1 of 3 tasks
fruitymedley opened this issue May 24, 2024 · 0 comments
Open
1 of 3 tasks

Make Pagination Optional #167

fruitymedley opened this issue May 24, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@fruitymedley
Copy link

fruitymedley commented May 24, 2024

Currently, pagination is configured for a model automatically if any relationship contains uselist=True, as seen in mapper.py:389. This seems undesirable as a strict rule, particularly in cases with a one-to-few relationship (think tires on cars). Obviously, there are cases where pagination is desirable (such as navigating a e-commerce catalog), so pagination should be toggleable.

Feature Request Type

  • Core functionality
  • Alteration (enhancement/optimization) of existing feature(s)
  • New behavior

Description

  • Add a flag for pagination, which, when True, configures the schema using relay pagination for the field, and, when False, creates a simple array of objects for the field

Upvote & Fund

  • We're using Polar.sh so you can upvote and help fund this issue.
  • We receive the funding once the issue is completed & confirmed by you.
  • Thank you in advance for helping prioritize & fund our backlog.
Fund with Polar
@fruitymedley fruitymedley mentioned this issue May 24, 2024
11 tasks
@Ckk3 Ckk3 added the enhancement New feature or request label Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants