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
When cancelling changes for a "dirty" SQFormDialog form, we clear out the form so the user can start with fresh inputs with their next attempt. This same clear isn't run when the primary/submit/save button is selected and the dialog is closed out. For our work on SRTS 2, we would like the option to run this clear when following the primary button user flow.
This could take the form of a prop flag that by default would be false, but if set to true would clear the form after the primary button is selected.
Instead of capturing this behavior in the component, @20BBrown14 has suggested utilizing the formikBag interface that's exposed when running the onSave or onSubmit callback to control clearing the form and any other desired behavior that happens alongside the primary button selection.
When cancelling changes for a "dirty" SQFormDialog form, we clear out the form so the user can start with fresh inputs with their next attempt. This same clear isn't run when the primary/submit/save button is selected and the dialog is closed out. For our work on SRTS 2, we would like the option to run this clear when following the primary button user flow.
This could take the form of a prop flag that by default would be false, but if set to true would clear the form after the primary button is selected.
Here is a loom unpacking the issue: https://www.loom.com/share/7644c1f7bbcb4ba88d1aa12c122fa6e8
The text was updated successfully, but these errors were encountered: