You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 30, 2018. It is now read-only.
Sometimes we use the formData to transfer information thorough the form structure that is not actually relevant. Some examples would be:
Typeahed uses "field_name_typehead" when the id transfered is not the same as the title displayed.
DynamicForm uses "field_name_form_def".
I think it would be ideal to have a metaData data object that is transferred to the input elements, this can be updated by DataSourcedMixin, and then other form elements can react to those changes.
The text was updated successfully, but these errors were encountered:
Instead of storing "options" and other sourced data as state, we should propagate it to the parent component (as we do with formData).
I'm still not certain where the data resolution should be done. Whether pass "formData" + "dataKey" down the line or just pass the "data" itself. (same thing regarding metadata).
Sometimes we use the formData to transfer information thorough the form structure that is not actually relevant. Some examples would be:
I think it would be ideal to have a metaData data object that is transferred to the input elements, this can be updated by DataSourcedMixin, and then other form elements can react to those changes.
The text was updated successfully, but these errors were encountered: