@misha with all due respect point number 2 is absolutely ridiculous.
I can accept that we can’t use the value of a resource input for another setting’s visible if condition. However, the fact that resource inputs are completely blocked off from visible if, is just insane. I don’t mean to ask too much but I think the community needs some detail on this as to why this is the way things are at the moment. We have an explanation for point 1, so what about point 2?
Regardless of visible if hiding or showing an input our liquid code already has to handle fallbacks and managing input data when the conditions have it hidden. So it can’t be something like “well it’s just a data point we wouldn’t want to have hidden but still referenced in code”.
Honestly it seems like a blatant code mistake that the resource input types were just blanket excluded.