Cannot order alphabetically about sortable HOT 9 CLOSED

I’m fairly confident the issue is that Date.parse('1&1') returns the current date in Chrome whereas Firefox returns NaN. This is the imperfect criteria we use to decide if a column contains “date” data. We could introduce an attribute data-sortable-type which you could add to the th to force a specific data-type to Sortable, with current options numeric, alpha and date. For the time being though if you ensure that the entry in the first row of the “Host” column (call it foo) have a value such that Date.parse(foo) returns NaN, you should see this issue resolve. Hope this helps!

from sortable.

Turns out someone already suggested this in #21. This should be closed as a duplicate.

from sortable.

(I’d close it myself but no longer have admin privileges for some reason.)

@timmfin @geekjuice @TrevorBurnham @graysky a little help here?

from sortable.

Thanks @timmfin

from sortable.

@adamschwartz I'm working on an implementation that allows selecting the sort order via data-* attributes and also allows the user to add custom types and/or change how the types work. It has been pretty hard not to break BC and to keep the small footprint at the same time, but I think I'm getting there!

from sortable.

@felds Thanks, cool idea. Since window.Sortable.types and window.Sortable.getColumnType are already exposed, you could probably modify getColumnType slightly and you’d be pretty close. Hope this helps.

from sortable.

@adamschwartz
I made so that each type test the data to see if it matches its definition. (felds@f28945f)

It works, but it's not that easy defining new types, as it's not an object, but an array (so pushing a new type would append it to the list, after the default one).
Converting the array to an obj flips the problem: we cannot trust the obj order when iterating through its keys and the default type could come first on the loop.

I think a solution could be adding a "priority" key to the type obj, converting the types obj into an array before looping and then sorting by that property. Not that elegant, but I think that would work!

Any ideas?

from sortable.

Great idea! I think the array option is slightly better. See my couple comments, but I can’t wait to see the PR! Nice job. And thanks! 👍

from sortable.

Ran into this issue (that as mentioned above only occurs in chrome) due to it thinking any number is with a string is a valid date. Has anyone found a way, other than data-sortable-types in getting around Chrome's different way of dealing with Date.parse / new Date's?

from sortable.