Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-5660

CanMove rule should reuse the logic from DropConstraint

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Won't Do
    • Neutral
    • None
    • None
    • framework
    • None

    Description

      Currently the CanMove rule implements its own logic separate from the of the DropConstraint. Since both classes deal with move actions we should try to reuse the latter from the former instead of duplicating the logic.

      This should also solve the current problem with CanMove only receiving the first source item of a move action - even when multiple are selected.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              mduerig Michael Duerig
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Task DoD