Skip to content

distinguish between "no results" and "results loading" #146

Description

@vincerubinetti

Currently, my placeholder messages distinguish between "not enough input" (eg, no source or target node selected so we can't show metapaths) and "no results to show" (eg, there are no paths for the selected metapaths).

But it'd also be good to have a separate "loading results" message for when the necessary inputs are selected, and there might be results, but we're still waiting for the backend query to return or for the frontend to render a big table. This gives the user good feedback that they haven't done something wrong, and the true state of the application.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    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