Skip to content

Suggestion: formalize state of data acquisition #5

@jmbldwn

Description

@jmbldwn

If more than one component needs data at the same time (peers on a page, for example), the test on whether the data has been loaded (it's not null) fails and multiple actions are performed in parallel, unnecessarily.

If each action could keep state (empty, loading, error?), we could skip actions that are repeats of actions in progress.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions