Currently, Auth.Flow.init takes a toBackendFn to turn the produced Auth.Common.ToBackend to an arbitrary Cmd msg. Auth.Flow.signInRequested, however, does not, necessitating it always be followed by a Tuple.mapSecond toBackendFn.
It feels as if either both or neither of these should take a toBackendFn parameter (both probably being the more ergonomic option).
Currently,
Auth.Flow.inittakes atoBackendFnto turn the producedAuth.Common.ToBackendto an arbitraryCmd msg.Auth.Flow.signInRequested, however, does not, necessitating it always be followed by aTuple.mapSecond toBackendFn.It feels as if either both or neither of these should take a
toBackendFnparameter (both probably being the more ergonomic option).