Now we’re talking
This is pretty much how it’s gonna be except Invalid(option('message))
b/c there can be no massage at all + message might be i18n object instead of string. And this data is stored inside formality container as a Map
w/ field
as a key and option(fieldStatus)
as a value.
I think we can leave list
out of our scope as message
type is defined by user, for us it’s abstraction: what we receive is what we store and return. We just pipe it to UI in the right time. So user might define type message = list(string);
. Does it makes sense?
That prolly also ok. Need to play around w/ it a bit but after Valid
/Invalid
change.
BTW what is option(string)
?
Makes sense! Moving meta to user land also makes it sound as it’s possible to use variants instead of strings.