You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] bug report => Search github for a similar issue or PR before submitting
[ x ] feature request
[ ] support request => Sorry, we will not be able to answer every support request. Please consider other venues for support requests
Current behavior
Currently the drop event emits a dropIndex but a dragIndex is not emitted in either the drop of drag events
Ideal behavior
Both the drag and drop events have a dragIndex to identify the index of the dragged item in the array.
What is the motivation / use case for changing the behavior?
Enables sorting other arrays reacting to the change in the model array.
Please tell us about your environment:
ngx-dnd version: x.x.x
5.0.6
Angular version: 2.x.x
5.2.10
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
Language: [all | TypeScript X.X | ES6/7 | ES5]
The text was updated successfully, but these errors were encountered:
mkelly95
changed the title
Add dragIndex to drag event
Add dragIndex to drag and drop event
Oct 3, 2018
I'm submitting a ... (check one with "x")
Current behavior
Currently the drop event emits a dropIndex but a dragIndex is not emitted in either the drop of drag events
Ideal behavior
Both the drag and drop events have a dragIndex to identify the index of the dragged item in the array.
What is the motivation / use case for changing the behavior?
Enables sorting other arrays reacting to the change in the model array.
Please tell us about your environment:
ngx-dnd version: x.x.x
5.0.6
Angular version: 2.x.x
5.2.10
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
Language: [all | TypeScript X.X | ES6/7 | ES5]
The text was updated successfully, but these errors were encountered: