The supportingWidgetDefaults property of the Editor Widget defines featureForm as an array of optional fieldConfig objects. However, the fieldConfig object of the FeatureForm widget is depreciated. (source)
Shouldn't the supportingWidgetDefaults property be updated to support a featureForm with an array of FieldElement and/or GroupElement objects? Or, maybe a formTemplate object?
Problem:
I'm looking for a way to change the Editor's template based on workflow. If a user is updating, the fields should be configured differently than if a user is adding. It is a bit confusing if this should be managed by supportingWidgetDefaults as the documentation supports using a depreciated object model.
