Skip to content

Hat migration for "bring" / "move" #526

@pokey

Description

@pokey
  • Automatically move the hats from the source to the target immediately after a "bring" / "move". This approach would result in a single hat corresponding to multiple locations in the case of a single-source-multiple-destination broadcast move (eg "bring funk air to after bat and cap")
    • We could create an alternate term for the source hats as well, eg "source gust", etc
    • Alternately we could leave the old hats and have the new ones be called "that gust" or "new gust"

Note: This behaviour already occurs with "clone"

See #414 for more context and an example use case

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    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