Skip to content

Multiple calls on itemsChanged when using update: 'itemsChanged', and changing between lists #9

@PatrikSoder

Description

@PatrikSoder

I noticed since i want the model to be backed by a MVC API - application in the back.

However changing to a call on stop: 'itemsChanged' instead helped me for now ( i have to test further)

My version :

angular.module('ui').value('uiSortableConfig', {
sortable: {
connectWith: '.connectedSortable',
//update: 'itemsChanged',
stop: 'itemsChanged',
}
});

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions