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
I like the approach using StrawberryConfig, as well as the per-field settings - both can be valid use cases (e.g. nested fields with filters on a nested connection). @bellini666 what's your take on this?
@Eraldo happy to review any PR on this if you have the time to push something 😊
I like the approach using StrawberryConfig, as well as the per-field settings - both can be valid use cases (e.g. nested fields with filters on a nested connection). @bellini666 what's your take on this?
Me too! Makes sense in my head.
I would maybe just call it max_results, as it is already a field that will exists only in the connection function, meaning relay_ is already implied. (but no strong feelings)
@Eraldo happy to review any PR on this if you have the time to push something 😊
+1
I also think we should have this for defaults in relay
We already have the schema config one, I think the only one missing here is the per-field one.
Feature Request Type
Description
Current:
The maximum of returned results for a relay connection defaults to 100 and can be changed by a schema wide setting:
strawberry/strawberry/schema/config.py
Line 14 in b7f2881
Example:
Improvement:
The maximum results returned can be overwritten on a per field level via a field setting.
Example:
Upvote & Fund
The text was updated successfully, but these errors were encountered: