-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
form-js-viewer
refactor, splitting view and state management
#1166
Comments
We are currently considering to build two sub-packages to handle the separation. These would be independent from each-other which means that you could either use the core package with a custom renderer, or the renderer package with any type of schema corresponding to the visual contract we want to build up between the two packages. I briefly sketched out how we see the core architecture's direction (early ideas anyways). But we could opt for a near-stateless transformation pipeline that would look something like this: The advantage of a pipeline like this would be that it would simply eliminate side-effects, and make the forms truly deterministic relative to the only thing that can actually change within it (the managed form state). |
What should we do?
We need to split the
form-js-viewer
state management logic from its rendering in two different projects.Why should we do it?
There are many motivations for this change:
How we are going to do it?
form-js-render
package #1189form-js-viewer-core
package #1208Internal discussions ongoing, see comments for the brainstorms.
The text was updated successfully, but these errors were encountered: