Simon Bobrov

Hi, would be super then if you create the stackblitz that reproduces the issue. It’s hard to help otherwise...

The library was renamed and further developed. Probably the issue you are facing is a mismatch between the versions of ngx-sortablejs and sortablejs

Hi @ScottMGerstl thank you for a very detailed description. Which version of sortable library do you use? If 1.8+ then could you try whether it is reproducible with v1.7.0?

hi @ScottMGerstl thank you for investigation. This is a weird behaviour... Is there a public repository the issue can be reproduced? It's hard to say anything without trying and failing...

Hi @Federen for me changing `sort: false` to `revertClone: true` and removing the `clone` from the target list (looks like) solved the problem ```ts normalOptions1: SortablejsOptions = { group: {...

Hi @serjo96 the directive accepts either Array or FormArray. In your case you pass an observable `[sortablejs]="todos$"` which is of course wrong: observables are not yet supported (might be a...

@serjo96 Don't pass anything and it will stop attempts of slicing the things (e.g. ``) but you would be left with the implementation of onUpdate / onAdd / onRemove on...

yes, something similar to this, in particular [sortablejsOptions]='{ onUpdate: yourOnUpdate }' where onUpdate will be passed to the original library https://github.com/RubaXa/Sortable

Please note that onUpdate manages the updates of the current list only. If you drag / drop from / to different lists you need to use onAdd and onRemove additionally

@serjo96 you have an array that is rendered with `ngFor`; just take this array in onUpdate event... See https://smnbbrv.github.io/angular-sortablejs-demo/custom-options or its implementation https://github.com/smnbbrv/angular-sortablejs-demo/blob/master/src/app/examples/sortable-with-options/sortable-with-options.component.ts