Skip to content

Using sorted_y could lead to incorrect data interpretation #5

@tayaza

Description

@tayaza

Hi there. Just realised a situation where using sorted_y could show misleading information as shown below.

Figure 1 (sorted_x='d', sorted_y=None)
Image

Figure 2 (sorted_x='d', sorted_y='d')
Image

Figure 1 is correct, Figure 2 is not. While, sorted_y correctly orders the horizontal bars and names, the order of the intersection dots and vertical bars is not changed. This shows Email with the intersection sets of Address, which is misleading.

Are sorted_x and sorted_y mutually exclusive? If so, can we implement a mechanism to prevent using them together?

Thanks for creating this!

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