field level relay results limit about strawberry

[erikwrede]

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 😊

[erikwrede]

I also think we should have this for defaults in relay

[bellini666]

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.

[stygmate]

+1
Same need here. I need to make results length unlimited for a field while protecting others.

[stygmate]

All seems to take place here:
/relay/utils.py:137

We can add a parameter to the field and get it here if it's set.