Why not to use slots?

[PlkMarudny]

Why not to use slots for rendering list items?

[jwlarocque]

I didn't use slots primarily because I didn't anticipate that doing so would be useful. The original design scope of this component was simply to provide the end user a way to order a list of strings.

Additionally, this component relies on carefully controlled pointer events. Providing more opportunities for list items to be interactive also provides more opportunities for problems with the drag and drop behavior.

Anyways, please tell me more about why/how you would like to use slots - I want to make this component as useful as possible.
You are also welcome to suggest an implementation or submit a PR if you would like.

[PlkMarudny]

This is what I use:

I am passing down another component, with the input, three checkboxes, and a few labels. My component fires several events to be served by a component up in the hierarchy.
What I did at the end was changing the source of your great component to implement this. Had to disable events on the input, as I discovered some strange side effects while dragging via input element. No slots used. Initially was under impression slots would had been enough.

[nicknack23]

+1 for slots. I want to use this to make a sortable file tree, where nodes can be folders that contain other nodes. So I need full control over the "list elements" (and would scrap the up/down and delete buttons). Ergo I need slots.

[elimisteve]

@nicknack23 This fork appears to have made some of the enhancements we're looking for: https://github.com/Lindsay-Needs-Sleep/svelte-dragdroplist

[PlkMarudny]

I found using svelte-sortable easier after all. You can simply pass a component to your list item, this is demonstrated here REPL.

[Kauto]

@jwlarocque +1 for slots. I would use it like the html attribute in the objects. For me it's cleaner this way to format the objects. F.e. I want use flexbox to show title of music on the left side and the duration on the right side.