Allow visibility condition to be set if question is unanswered about civiform HOT 3 OPEN

@Miguel-314 FYI! I'll plan to add some more of the technical details I found when looking into this as well

from civiform.

This is where we decide whether to show / hide a block:

This is where we make sure there is something selected in the predicate UI:

When nothing is selected, the predicate doesn't match either of these key patterns because the predicate value is empty:

from civiform.

The reason this is complicated is because if a question hasn't been seen / answered, the response won't be added to the applicant data (

So my applicant data may look like this because I've only seen one question {"applicant":{"treeqdk":{"updated_at":1714146723403,"program_updated_in":7,"selections":["1"]}}}

But the predicate will look like this: $.applicant.sample_checkbox_question[?(@.selections noneof ["3", "2", "1"])]

So if the sample_checkbox_question is not in the applicant data, it won't be compared no matter what.

If an optional question is skipped, it is entered as so: {"applicant":{"treeqdk":{"updated_at":1714148097313,"program_updated_in":7}}}

We can consider either allowing for empty predicates to be set and if its empty we'd check that its absent or empty (like the optional situation above)

Maybe this would look something like !$.applicant.sample_checkbox_question || !$.applicant.sample_checkbox_question[?(@.selections)]

I think this would involve adding a new operator type of EMPTY or something like that

from civiform.