Hidden computed fields

[aerni]

I've got a events computed field in a community collection. I don't want to show this field in the CP. The simple solution is not to add the field to the blueprint, dah. But I still want to make use of field augmentation, which is why I'm adding an events field to the blueprint.

But if I choose visibility: hidden, the value gets saved. And if I choose visibility: computed, the field is shown. It would be great if we had the option to also hide computed fields in the CP.

Maybe visibility: hidden should work like conditional fields and not save values by default. And you can opt-in to saving values with always_save: true. Then we could probably remove the visibility: computed option, as the only difference is that it doesn't save values compared to visibility: hidden. Just an idea.

The simple workaround is to add a field condition in addition to visibility: computed. Something like:

if:
  this_will_never_show: 'equals true'

[jesseleite]

Good use case, but we disagree with changing the functionality, as there are also valid use cases for how it's currently designed as well.

That said, how about if visibility: hidden was intelligent about detecting whether or not it's being used on a computed field?

[aerni]

That should work.

[o1y]

I have a similar use-case, where I just want to show my computed field in the listing only, but not on the publish form. Having visibility: hidden, would save the computed value.