We have a scenario where we have inputs inside the sortable component. As the user types into the input the focus is lost constantly this is due to the Sortable component being re-rendered unnecessarily by Angular change detection. You can see an example here

Angular is moving towards immutable data structures and it is often the recommended practice. Therefore I believe the sortable component should be able to handle the scenario provided. This should be achievable by internally using a trackBy function to help Angular recognise when data hasn't changed. This should be accompanied by allow the consumer to provide their own function for tracking.

A similar issue was raised 5 years ago but wasn't adopted. In my opinion given the massive advancements in Angular and the introduction of Signals this becomes a more pressing issue now and arguably moves from the realm of feature request to bug.

Currently, it is very difficult to get the Sortable to use Angular components as child items.
It would be great if it supported this.

DragEnd event should be fired when user ends a drag. Now this event is being fired when user is moving element in only one component.

I attach example in plunker. Please notice that there is event handler for dragEnd event. To test this please move colors in one pallete and between two palletes.

https://plnkr.co/edit/yED4zBX9R7lf75jZnlrq?p=preview

Best regards,
Pawel