Radio component defaultValue changes to null after saving. Instead of the desired: "".

[LaurensBurger]

Product versie / Product version

3.0.4

Customer reference

reported by: DH, hlm, Ensc

Omschrijf het probleem / Describe the bug

When you add a radio component to a step, the initial defaultValue is set to: "".
By saving the component the defaultValue gets changed to null.

The issue with null is when this radio is hidden with "empty when hidden" is enabled, the component is included in the check_logic as "radio": "", which in turn triggers validation for the step with no user interaction. Unfortunately this issue is pretty prevalent across environments.

After manually changing the null back to "" in the json of the radio component - this validation triggering is no longer an issue.

Verwacht gedrag / Expected behavior

i expect the defaultValue to not cause validation to trigger when a step loads

Screen resolution

None

Device

None

OS

None

Browser

No response