Allow functions for relationTo, maxRows, etc.

[n-a-t-j-b]

Hi team, are there any plans to allow additional config properties to be functions? Our primary concerns are with relationTo and maxRows but there may be other edge cases e.g. max/min, readOnly etc. Not looking to change the nature of the field as the function should still have to resolve to a valid typed value.

Our need for a dynamic relationTo - so that our Author field value can determine which upload collection to assign to an images field.
Our maxRows use case: resolves to 10 or 1 for that same images field, based on our Author field relationTo value.

Full scenario and solution today:

• Author field: relationTo: ['partners', 'users'], uses a filter based on logged in user permissions to determine which ids are valid values - note this works fine and results in: author: { relationTo: '', value: ''}
• Images: 2 fields currently in use to enable collection selection for upload and maxRows (based on author type), i.e.
  • partnerImages (all publicly visible): upload field with relationTo 'partnerImages', maxRows: 10, condition: author.relationTo === 'partners'
  • userImages (no public visibility, limited authenticated visibility): upload field with relationTo 'userImages', maxRows: 1, condition: author.relationTo === 'users'

Our current options (ones we've evaluated at least):

1. Hook to take data from the correct conditional image field values and save it to a 3rd "hidden" field (of 'relationship' type so it can allow multiple collection options) with relationTo: ['partnerImages', 'userImages'], maxRows:10 - this makes frontend rendering simpler by using a single field but duplicates data; or
2. Accept more complex image rendering based on the other data values in the doc.

Either way, not ideal, whereas a single images field (like our author field) would definitely simplify logic and reduce the need for additional db storage.

Would love some feedback on this - if there's currently an alternate way to do what we need or even just better logic to deal with our use case.

Cheers, Nat.

Edit: initial post suggested hasMany but given that would change the item structure from a single object to an array, we've resolved to use maxRows instead with a practical limit for both collections.