-
Bug
-
Resolution: Unresolved
-
Undefined
-
1.8.0
-
None
Description of problem:
fetch:response:value always overrides the widget’s default value, which makes it impossible to start with an empty field. We need support for keeping the field empty until the user explicitly selects a value. Specifically:
- Add a config option like fetch:skipInitialValue: true to prevent setting an initial value
- Treat fetch:response:default: "" as a valid default
- Allow fetch:response:value to resolve to an empty string from JSONata expressions
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
# <steps>
Actual results:
fetch:response:value always overrides the default and forces a value, even when we want the field to be empty.
Expected results:
The field can start empty even when fetch:response:value is configured, and empty-string results from JSONata are respected.