We have a use case where we'd be building a custom editor which ideally would, based on the current value of the field the editor manages, set the values in some other fields and then disable/hide the fields, to prevent editing those values. For some other values of the custom editor field, the values should remain changeable
It seems like the setting values would work, but the disabling/hiding the editors would not, with the current api's. It would be nice if it did.
I'm also feeling like there's probably some work around possible for our use case where we react on the other fields changing by resetting the correct values we want to be there.
And from reading some of the responses, probably some secret additional way, where we replace all the fields, and make them set their state based on the original field instead.
Those all do feel like they add more complexity and make our contnetful space more complicated to maintain with all the additional custom fields.
We have a use case where we'd be building a custom editor which ideally would, based on the current value of the field the editor manages, set the values in some other fields and then disable/hide the fields, to prevent editing those values. For some other values of the custom editor field, the values should remain changeable
It seems like the setting values would work, but the disabling/hiding the editors would not, with the current api's. It would be nice if it did.
I'm also feeling like there's probably some work around possible for our use case where we react on the other fields changing by resetting the correct values we want to be there.
And from reading some of the responses, probably some secret additional way, where we replace all the fields, and make them set their state based on the original field instead.
Those all do feel like they add more complexity and make our contnetful space more complicated to maintain with all the additional custom fields.