Skip to content

Logic for grouping cards #190

@keanelekenns

Description

@keanelekenns

This might be tricky, and it is debatable that it is needed. I see two approaches:

  1. Cards are grouped by having the same non-unique settings
  2. Cards are grouped by the initial grouping created by the user when adding the resource (I believe this will be easier)

Approach 1 requires the page to search through existing resource cards upon changing/creating a card. If there are similar settings, the changed/created card gets added to the found card (either multi or single).

Approach 2, simply bunch the resource cards together when they are created using the "Number of Instances" option, and always keep them together regardless of their settings.

Approach 1 seems to be a nicer organizational method, but that may depend on what the user wants + it is more tricky to implement.
Approach 2 gives the user more control over how resources are bunched together (in approach 1, they might accidentally set a resource up exactly the same as another resource and be confused when those two get put into a multi-card, but this approach doesn't have that issue, they are in control)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions