Usage on an Single Asset field causes Display Editor to become locked; unable to switch back to default about datocms-plugin-computed-fields

[velomovies]

Hi @arcataroger thanks for the heads up and nice to see that's fixed!

One of the main things we consider with this plugin is that there should be no limitations regarding the possibilities. I think there are ways to implement this in a single-asset field, but that's for the users to figure out themselves. It should open endless ways to implement it and have the freedom to use it if you need it. So thats why I don't want to exclude this field type.

[arcataroger]

I've also reported this issue internally, and will report back here if we find any additional information.

[arcataroger]

@voorhoede We shipped a fix for this internally, so users can revert fields back to the default editor if need be.

But do you think there is a legitimate use case for single-asset fields being able to be displayed as a Computed Field? I'm asking just because I wonder if it would be safer to exclude that field type from this plugin altogether. What do you think?

Thanks again for your work on this!

[arcataroger]

Gotcha. Thanks for the explanation!