You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 (thinktire
s oncar
s). Obviously, there are cases where pagination is desirable (such as navigating a e-commerce catalog), so pagination should be toggleable.Feature Request Type
Description
True
, configures the schema using relay pagination for the field, and, whenFalse
, creates a simple array of objects for the fieldUpvote & Fund
The text was updated successfully, but these errors were encountered: