hoverCallback's bug

[ghost]

let's say, we use data like "[{date:2013-07-13,value:'node A'},{date:2013-07-12,value:"node B"}]".
Morris will order the nodes again, to show them in right order.

But the for the "hoverCallback" method:

hoverCallback: function (index, options,content) {
var row = options.data[index];

if i choose the second node which's date is 2013-07-13, the index value will be 2, but the "options.data" is still the original data.

[sudodoki]

Okay, so main culprit here is probably, this line
https://github.com/oesmith/morris.js/blob/master/lib/morris.grid.coffee#L182
The question arise: should callback arity be changed or should we modify options.data as well as data?

[oesmith]

Since the indices get all messed up by the sort, I've added an extra parameter to the hover callback. See https://github.com/oesmith/morris.js/blob/master/examples/decimal-custom-hover.html#L182 for an example of the new param.