Skip to content

Conversation

@winged
Copy link

@winged winged commented Jan 14, 2025

We don't need to ensure that every dependency is non-hidden; indeed it should be possible to evaluate an expression where parts of the dependencies are not set. This is how the backend does it. Also, the answer transform does have a default option, so we should easily be able to deal with this.

We don't need to ensure that *every* dependency is non-hidden; indeed it
should be possible to evaluate an expression where parts of the dependencies
are not set. This is how the backend does it. Also, the `answer` transform
does have a default option, so we should easily be able to deal with this.
The answer transform should behave exactly as follows:

* Field does not exist: return default value, or empty
* Field is hidden: Return empty value
* Field is unset: Return default value or empty
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant