Skip to content

Best practices to present error when there are viewable and not viewable flow #41

@alexvbush

Description

@alexvbush

Original issue: uber/RIBs#160

Let's suppose we have:

SignIn (viewable) -> SignInProcessA (not viewable) -> SignInProcessB (not viewable)

Supposing that in SignInProcessB Interactor we had an error, I have some questions:

  • It should call a method from it's listener i.e: self.listener?.hadErrorSigningIn(error) recursively until it arrives at SignIn (viewable) to use presentable like: self.presentable.present(error)?

  • If above answer is right, should I call something like:

    self.router.detach(animated: true) {
    self.listener?.hadErrorSigningIn(error)
    }
    in order to grant that everything was detached when it arrives at SignIn(viewable) ?

Thanks in advance...

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