Properly hide or disable the field about datocms-plugin-computed-fields HOT 4 CLOSED

Hi @JanStevens thank you for your contribution, we'll get back to you :)
Hiding is already a feature right? Do you mean not rendering the title too?

@velomovies thoughts on rendering the field as disabled?
Can imagine not rendering the title could be nice but also could lead to confusion where data is coming from?

from datocms-plugin-computed-fields.

@Siilwyn I indeed mean not rendering anything at all (see related issue: #19 (comment))

At least we should render the field disabled to clearly indicated to content editors this is an auto generated field

from datocms-plugin-computed-fields.

Hi @JanStevens,

For hiding the field we already returned nothing in the previous version. I've changed that to returning null instead of a Fragment.

In your example you use the hideField function from Dato next to returning null. That works great in your example, but not in this case. The hideField function will not render the form input, and makes it so the plugin doesn't rerender when something changes in the other fields. Therefore the value of the computed field will not update automatically when you change other fields in the model. The automatic update is something we very heavily rely on and don't want to break when hiding a field.

Showing the field as disabled is a great addition and will be implemented when we update the plugin.

from datocms-plugin-computed-fields.

Allright that sounds great!

from datocms-plugin-computed-fields.