Skip to content

Multiple fast requests leave the table in inconsistent state #7

@jpbottaro

Description

@jpbottaro

Since the ordering of the incoming responses of parallel requests is unknown, and the table is updated when the 'reset' event is fired in the collection, it can reach inconsistent states.

We should only care about the last request (as per user input), and cancel/ignore the rest.

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