Improve type checking for defaultValue with hasMany: true

[PatrikKozak]

Currently, fields like text, number, select, and relationship with hasMany: true accept a defaultValue of any SerializableValue without type errors.

Since these fields expect arrays when hasMany: true, it would be more intuitive and type-safe for defaultValue to explicitly require an array in these cases.

Example:

{
  name: 'selectWithDefaultValue',
  type: 'select',
  hasMany: true,
  defaultValue: 'one', // This should ideally throw a type error.
  options: [
    {
      label: 'Value One',
      value: 'one',
    },
    {
      label: 'Value Two',
      value: 'two',
    },
  ],
},

The above should throw a type error since defaultValue should be an array when hasMany: true, like this:

defaultValue: [ 'one' ]

Proposed Change:

• Track fields with hasMany: true and enforce defaultValue to be an array of the expected type (e.g., string[] for text fields).
• This would apply to all fields with hasMany: true.

Considerations:

• This would be a breaking change, as it modifies the expected types for defaultValue.

[zacuke]

Even if I don't set a Default value, I still encounter the problem: The select field is pre-selected, but the validation is acting like it's not. The user must take action to manually select a different value, then go back and select the originally pre-selected value.

Also I'm never editing any json like that, are you saying that in the Admin interface instead of putting plain string Whatever in the default value field, I should be putting the json literal ['Whatever'] into the textbox inside the Admin interface?

[PatrikKozak]

@zacuke The example I shared above is referring to the payload collection config, not the admin interface. If you're using the Admin interface, you wouldn't need to enter JSON - this only applies when defining the field directly in your config file.

Regarding the issue with the select field being pre-selected but validation acting like it's not, sounds like a separate behavior worth looking into. If you're not using a defaultValue, could you please open a new issue here and share more details on the field setup?

I'd be happy to help troubleshoot that there!