Skip to content

Do not set arbitrary first value

Carlos Sanchez requested to merge 748-prevent-first-value into main

Yesterday I created !616 to ensure a valid setting value when setting or getting settings.
Thinking about it in the morning: I would remove this line, as otherwise we will always set a value, even if we want the defaultValue to be undefined/null as e.g. we do in the dataTransmissionPreferenceSettingsEntry.

Additionally I noted that on hcp site currently the Receive data is broken because of the change, as undefined is not part of the options.
This also lead to a infinite loop.
This PR

  • adds undefined as an option
  • prevents the infinite loop
  • does not set an arbitrary value

Merge request reports