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 Fable form is using the label of the field to keep track of their errors.
But I am not sure if this is the correct ways of doing it, I feel like we should explicitly ask the user for a unique ID and then have it provide the label of the field.
For example, this cause problem is you change how the checkbox is defined to accept either a string or a ReactElement for its "label"
typeAttributres=| Text ofstring| ReactElement ofReactElement
Then in the case of ReactElement we don't have the needed information to store the key of the field error. We need to change it to ReactElement of string * ReactElement.
This could be seen as a specific but I think it just shows that we have a wrong design in the current way we consider the forms.
The text was updated successfully, but these errors were encountered:
Currently Fable form is using the
label
of the field to keep track of their errors.But I am not sure if this is the correct ways of doing it, I feel like we should explicitly ask the user for a unique ID and then have it provide the label of the field.
For example, this cause problem is you change how the checkbox is defined to accept either a
string
or aReactElement
for its "label"Then in the case of
ReactElement
we don't have the needed information to store thekey
of the field error. We need to change it toReactElement of string * ReactElement
.This could be seen as a specific but I think it just shows that we have a wrong design in the current way we consider the forms.
The text was updated successfully, but these errors were encountered: