Skip to content

Examples of Error Handling #3

@namuol

Description

@namuol

Error handling is especially tricky with the Flux architecture. Namely, tracking and displaying errors in the View that occured asynchronously, such as failed server operations.

It would be useful to see how marty handles actions that have corresponding failure (and success) state, but in this example, server actions are 100% optimistic. ;)

After going through the docs a little, I found fetch which seems to have a very elegant approach to handling pending operations. The name suggests that it's only meant for READs, but it's unclear if that's the only use case.

Either way, this repo seems like the perfect place to illustrate an approach (if not the approach) to handling pending/failed operations in marty.

Cheers 🍻

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions