sorting problem - original order is not preserved even if sorting is not defined

hidegh commented 9 years ago

i go the json (below) as a result from remote. order is by 'bezna znacka/common brand' then by 'nazov/name'.

got these options:

            var options = {
                valueField: 'value',
                labelField: 'value',
                searchField: ['value'],
                sortField: '',
                highlight: true,
                maxItems: 1,
                create: true,
                createOnBlur: true,
                selectOnTab: true,
                addPrecedence: false
            }

but somehow order is messed up, conrete: index 1 (not 0) is exchanged with an item from the middle.

of course i could generate also a sort id from code and sort by that id, but that would be non-professional.

see image and json:

hidegh commented 9 years ago

Until then there's a possibility to do a more complex sort via options:

                sortField: [
                    { field: "value", direction: "asc" },
                    { field: "$score", direction: "desc" }
                ]

...but this is not a real solution, cause unnecessary sorting must be done on the client side...

brentkeller commented 9 years ago

I'm seeing a similar issue as well. The option at index 0 is being swapped with the option at index (options.length / 2) +1, the item just past the halfway mark. This only happens when there are more than 10 options in the list though. Setting the sortField options does get the list mostly in order but any items with diacritics aren't sorted correctly, which likely isn't a Selectize issue.

hidegh commented 9 years ago

Sorting is a tough issue, it's better to leave it to the SQL or programming language, cause each culture has it's own specific character order. That's why currently the orderId attribute is the only real solution :D

Anyhow thanx for confirming that the same problem occurs elsewhere.

brianreavis commented 9 years ago

I'm going to refactor $order sorting to not just be for options populated from the original DOM elements (coming soon).

Setting the sortField options does get the list mostly in order but any items with diacritics aren't sorted correctly, which likely isn't a Selectize issue.

This is fixed by the 0.4 release of Sifter.js, which will be used in the next release of selectize (coming in the next couple days)

Sorting is a tough issue, it's better to leave it to the SQL or programming language

Since the beginning, Selectize has been designed around client-side search and sorting for fast option selection. Using server ordering is possible, but it's going to be a hack. In the future we might have a preserveOrder option that totally bypasses the sorting, but I can't say that's an immediate priority. It'll need to be done in a way that doesn't add a bunch more branches to the code than there already are.

selectize / selectize.js

sorting problem - original order is not preserved even if sorting is not defined #640