🐎 revert natural sort

[billybonks]

fixes:
-#612
-#491
-#449 (tested with 9000folders, it was performant. should still make this async to increase cap)

[50Wliu]

I'll miss naturalsort a lot, but I guess performance is more important here.

[billybonks]

@50Wliu ill make a pr soon with a more performant sort, and a spec of what it should achieve. it will be a subset of what the other one did.

[50Wliu]

@billybonks 😍

[izuzak]

Friendly note: if/when this is merged, we should reopen #395 and #391. ✌️

[billybonks]

@izuzak good idea, opening one should be good enough.

[billybonks]

just a update on this i am changing the test, to dynamically check if the element is visible and in the correct place

[nathansobo]

I'm seeing a couple local test failures on this still. Seems like you may be on that already. Code looks good otherwise as it's a pretty simple removal.

[billybonks]

should be good to merge now, ill work on a faster natural sort soon

[nathansobo]

ill work on a faster natural sort soon

Awesome. Please ping me on that one as this was a nice feature, just not worth its present cost. Thanks for your help on this!

[MisterDA]

I was about to post an issue requesting natural sort when I realized there already has been a lot of on this. I would like to have this feature, even if it adds 17ms or so. Could you add a config option ? or something ?

[billybonks]

we already merged a very fast implementation of this. im not sure if it has
been shipped to beta. i use a master build for my day to day.

On Tue, Dec 8, 2015 at 6:56 PM Antonin Décimo notifications@github.com
wrote:

I was about to post an issue requesting natural sort when I realized there
already has been a lot of on this. I would like to have this feature, even
if it adds 17ms or so. Could you add a config option ? or something ?

—
Reply to this email directly or view it on GitHub
#616 (comment).

[lunarovic]

@MisterDA Natural sort is in stable as of today.