Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
MagicForm will help you manage your applications with microfrontend architecture, through the concept of isolated providers, for example:
Any action not registered by the provider will continue to bubble until the next provider.
Improves the form development experience thanks to the use of webcomponents to centralize submission
A powerful form submission manager created with Atomicojs webcomponents, with MagicForm you can:
Simplify the sending of forms by centralizing the sending actions through a provider.
Know at all times the forms that are being provided and show their status.
Isolate a group of actions according to provider, this means that if a provider does not register the action it will bubble to the parent provider.
magic-form-provider
captures all the forms nested in magic-form
when executing the submit event by the form and distributes them according to the definition of the action attribute to each method of the actions object
MagicForm makes it easy to send data to the server, here are some useful patterns
Type | Description | Config |
---|---|---|
Property | Description |
---|---|
"ChangeState"
Dispatched when status changes from provider
{bubbles: false, composed: false}
state
Read only, Current status submission of the form
Object
action
Defines the action to dispatch, if not defined it can be inherited from the
tag
String
"ChangeForms"
Dispatched when forms changes from provider
{bubbles: false, composed: false}
forms
Read only, current state of the captured forms
actions
object that defines the actions to be captured by the MagicFormProvider