Pass event down to onChange

[megawac]

Main reason I want to do this is to render a set of custom html elements rather than simple strings. Passing evt up lets me avoid a bunch of string parsing and instead just process the html element (just found out about data-id :)

Useful for desynchronized groups where you can add items to one group but cannot add items to the other; adding to the other removes from the second list

/cc @cheton

[cheton]

Thank you for your pull request. It looks good to me. I'll publish a release soon.

However, there are too many parameters in the onChange method, I'd try to refactor this part in the next major release.

[megawac]

Sounds good, I'm not sure if passing the sortable instance is really
necessary?

On Mon, Jul 18, 2016 at 11:25 AM, Cheton Wu notifications@github.com
wrote:

Thank you for your pull request. It looks good to me. I'll publish a
release soon.

However, there are too many parameters in the onChange method, I'd try to
refactor this part in the next major release.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#20 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADUIENZ6xgJ_Hi9n4O38nj2Wg5Pv0A6tks5qW5rvgaJpZM4JOweM
.

[cheton]

It's not necessary when using ref to store the sortable instance. I will plan to remove it as well.