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 field groups have withBoxedConverter, which can return a non-FullBox to indicate validation failures. There are, however, a couple of downsides to this approach:
The resulting failures have to be manually handled in onFailure, or the withBoxedConverter function has to explicitly invoke S.error to mark the client error.
The converter may produce an object of type T that is usually valid but isn't valid in the context of this form. This T may need further validation in this particular context.
Alongside Pushing validation side-effects later? #16, we could return a Failure of the same type that a field would, including attachment point information and error message information.
The text was updated successfully, but these errors were encountered:
Currently field groups have
withBoxedConverter
, which can return a non-Full
Box
to indicate validation failures. There are, however, a couple of downsides to this approach:onFailure
, or thewithBoxedConverter
function has to explicitly invokeS.error
to mark the client error.T
that is usually valid but isn't valid in the context of this form. ThisT
may need further validation in this particular context.Two things would help here:
T
type.Failure
of the same type that a field would, including attachment point information and error message information.The text was updated successfully, but these errors were encountered: