Current behavior
With 0.1.89 hakawati, we have introduced a new h-form that exposes a set of submit and cancel buttons as part of the h-form. These are currently set up to trigger any form validation on the input fields.
This conflicts with our h-dialog component or when we use standalone h-button and hook it up to h-from and we see both sets of buttons
If we decide to keep the buttons in the h-form we need to make the buttons not display by default so that way we can gradually refactor the buttons to use these. Currently about 20 files where h-form is being used
Expected behavior
We would like to decide does it make more sense to keep the buttons in h-form and remove it in other components like that h-dialog
Should we instead remove the set of buttons and emit the h-form validation so that it can be tied to individual h-buttons?
Current behavior With
0.1.89hakawati, we have introduced a newh-formthat exposes a set ofsubmitandcancelbuttons as part of theh-form. These are currently set up to trigger any form validation on the input fields.This conflicts with our
h-dialogcomponent or when we use standaloneh-buttonand hook it up toh-fromand we see both sets of buttonsIf we decide to keep the buttons in the
h-formwe need to make the buttons not display by default so that way we can gradually refactor the buttons to use these. Currently about 20 files whereh-formis being usedExpected behavior
h-formand remove it in other components like thath-dialogh-formvalidation so that it can be tied to individualh-buttons?