Skip to content

Consistency in whether Auth.Flow functions take an Auth.Common.ToBackend -> Cmd frontendMsg parameter #6

@SiriusStarr

Description

@SiriusStarr

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).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions