Skip to content
This repository has been archived by the owner on Jun 29, 2023. It is now read-only.

Enhancement: Support dragging items between Calcite Value Lists #1016

Closed
Csmith246 opened this issue Jun 16, 2020 · 3 comments
Closed

Enhancement: Support dragging items between Calcite Value Lists #1016

Csmith246 opened this issue Jun 16, 2020 · 3 comments
Assignees
Labels
1 - assigned enhancement New feature request for an existing component

Comments

@Csmith246
Copy link

Description

Support the ability to drag a Calcite Value List Item from one Calcite Value List to a different Calcite Value List.

Acceptance Criteria

  • List Item can be dragged between different lists.
  • Make that cross list movement accessible.
  • Expose helpful event hooks for the move operation.

Relevant Info

We have already implemented this by using private properties on the Calcite Value List. This implementation can be viewed here. The way to implement the cross list dragging is to give two Calcite Value Lists the same group name. So maybe it would be helpful to expose that group name as an input property on the Calcite Value List? The SortableJS events that were used in our implementation were onAdd and onRemove. So, I would say, consider exposing these (and maybe other) events, so that developers can have hooks to use to support any in app behavior that happens from a cross list drag.

Which Component

Calcite Value List, and Calcite Value List Item

Example Use Case

We are using the Calcite Value List to create a widget that allows users to position and order map widgets on the mapView ui. Our implementation can be viewed here

@Csmith246 Csmith246 added 0 - new enhancement New feature request for an existing component labels Jun 16, 2020
@jcfranco jcfranco self-assigned this Jun 16, 2020
@jcfranco jcfranco added this to the Ocean Princess milestone Jun 16, 2020
@driskull
Copy link
Member

I can help with this as need be. We probably don't want to expose the Sortable instance at all incase we change libraries in the future.

@jcfranco
Copy link
Member

#1006 may have an impact on this.

@jcfranco
Copy link
Member

jcfranco commented Aug 25, 2020

Addressed by #1059.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
1 - assigned enhancement New feature request for an existing component
Projects
None yet
Development

No branches or pull requests

3 participants