Repository navigation
Svelte Sortable drag-and-drop list doesn't update when Svelte Store changes #1946
Description
I am building a component using Svelte in which you have a list of words and you have to arrange them in the correct order by dragging the words to the answer section, for this, I am using SortableJS.
To store the answer and the words you can use I use svelte stores and everything works correctly. Now, I am trying to do the same but with an ʻonClick` event. But I have a bug where the store values are updated but the view does not.
To show the options and the answers I am doing this:
<div
class="chips"
use:sortable="{{ items: answer, options: { group: 'chips', forceFallback: false } }}"
>
{#each get(answer) as chip, index}
<span class="chip" on:click="{handleAnswerClick(chip, index)}">
<spain class="tag is-medium">{chip}</spain>
</span>
{/each}
</div>and if I replace the get in {#each get (answer) as chip, index} with $answer, the ʻonClick` event works but now the drag behaves strangely and with bugs.
Here is a codesandbox with both of the alternatives explained above
Reproduction
Scenario
https://codesandbox.io/s/sortable-bug-0lmd8
Version
| package | version |
|---|---|
sortablejs |
1.12.0 |
@types/sortablejs |
N/A |
Activity
waynevanson commentedon Oct 21, 2020
Sortable is a one way binding, where Sortable is the controller. It doesn't listen to your data.
This is unfortunate. AT the time of this being created, data driven development wasn't considered for this project.
kantord commentedon Oct 22, 2020
@waynevanson is re-creating the sortable js instance every time the data changes a viable solution?
waynevanson commentedon Oct 22, 2020
Check out Store in the read me. That might do what youre after. I've never used it myself.
samf commentedon Nov 16, 2020
@kantord did you ever figure this out? I'm running into the same thing, and my first attempts at recreating the sortable aren't working. I'm wondering if this is viable and I'm "just doing it wrong", or if it's never going to work that way.
kantord commentedon Nov 16, 2020
Hi @samf, not yet, I have been focusing on other things, and there's a lot of high prio things other than this.
Do you have some code example for your specific issue btw?
acoyfellow commentedon Mar 22, 2021
I can second this "issue". Working on a solution. Thank you for SortableJS, i enjoy using it
Demo:
https://svelte.dev/repl/9fe76dda194348d1acd6d2e336c30c22?version=3.35.0
edit: "solved" in a way i'm ok with:
https://svelte.dev/repl/3ca698f0c1064bd99667c9a7557c427d?version=3.35.0
Instead of mutating the original data object, make a copy upon initializing Sortable.. then, on sort, update the svelte data
janvotava commentedon Feb 11, 2022
If you don't mind little overhead, you can use the #key block now. Ideally you would probably implement Sortable as an action using
use:directive with adestroy()hook to not leave some memory leaks.Im-Madhur-Gupta commentedon Aug 21, 2023
Thanks @janvotava, your comment saved me. :)