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
Currently the form rendering layer is very coupled with the form mutation layer (FormFieldRegistry, PathRegistry) and this brings problems with reactivity/difficulty to maintain complex structures like groups and dynamic lists.
To try to solve that we should investigate on the possibility of refactoring and splitting the viewer into 3 different layers:
Core viewer, which would handle the mutation of the schema and provide fine grained subscription to these mutations
Preact/React compat library which provides primitives to trigger Preact rerenders when the form mutates
The component library with all the form elements we have today which would contain only each component's logic
This way we would also provide ways for other people to support libraries in vue, svelte, solid, etc while we would support only Preact.
Why should we do it?
The text was updated successfully, but these errors were encountered:
What should we do?
Currently the form rendering layer is very coupled with the form mutation layer (
FormFieldRegistry
,PathRegistry
) and this brings problems with reactivity/difficulty to maintain complex structures like groups and dynamic lists.To try to solve that we should investigate on the possibility of refactoring and splitting the viewer into 3 different layers:
This way we would also provide ways for other people to support libraries in vue, svelte, solid, etc while we would support only Preact.
Why should we do it?
The text was updated successfully, but these errors were encountered: