Columns are jumbled about rhandsontable

[jrowen]

Thanks for posting. The hand off between rhandsontable and htmlwidgets isn't working as expected, so I've posted an issue with that project as well.

[timelyportfolio]

I think changing this line to be explicit and follow ordering specified by x.colHeaders will be a more robust way to handle.

toArray(x.data.map(function(d){return x.colHeaders.map(function(ky){return d[ky]})}))

[jrowen]

Thanks, your suggestion fixes the problem and is more robust.

It appears to me that the column reordering is happening outside of the toArray call, as in the js debugger I see the x.data obj passed to toArray already has an incorrect order. It seems that js is reordering the obj values.

> x.data[0]
<- Object {4: 1, 6: 3, 8: 14, vs: 0}

Just trying to understand why this is occurring so I can prevent future bugs. Thanks again for the help.

[timelyportfolio]

I should in bold say I am not a definitive source but I recall seeing in multiple places that order of keys is not assured in JavaScript objects. Here is one StackOverflow post that seems to be more authoritative than me.

[jrowen]

Thanks for the link. I checked in a fix, but please re-open if you still run into issues.

[ramnathv]

If I remember correctly, the reordering occurs only when the keys are numbers.