Hidden components with "Multiple values" trigger validation

[LaurensBurger]

Product versie / Product version

latest

Customer reference

no particular but it get's reported

Omschrijf het probleem / Describe the bug

Hidden component with "Multiple values" set get their defaultValue changed from:

  "defaultValue": null,

to:

  "defaultValue": [
    null
  ],

This causes validation to trigger right after loading since their value is now [] instead of [ null ]

  "telefoonnummer": []

This can be resolved by changing the defaultValue to via the json of the components:

  "defaultValue": [],

[joeribekker]

Refinement: Task estimated here is changing the default value to an array ([]) without the null.

Robin can do this in an hour. So, let's timebox this to 2 hours. After that, the proper estimate is: (whatever Robin thinks)

[robinmolen]

I cannot reproduce this issue. I've followed these steps:

• Create a new form
• Add a radio button field, that isn't required, with a option
• Add a textfield, with the option multiple values and without defining a default value
  • (in the json this now indeed has the default value of [null])
• Add advanced logic to the textfield to only show if the previously defined radio has its value checked
• Save form and open it
• Go to the form step, keep the radio button unchecked, and go to the next step

[robinmolen]

I've made a PR that ensures that textfields always have a valid value (so null will be turned into '').

When a textfield (with the default value null) gets the multiple values property, the default value will change to [''].