Reverse Sorting Issues in Chrome about angular-tablesort

[mattiash]

Can you explain why you added the orderBy part of the filter? It will reorder the items in the array, but then tablesorter will reorder them again later in the filter.

[shawkenator]

Yeah, it's because of the additional sort buttons are little more complex than the table headers sorts. One example of the sorting buttons I need implemented says "Bring X to the top", now the value of X is coming through the service request, but isn't listed in as a table column. And to make it even more challenging, to sort the objects that contain this X value to the top, I have to do it in reverse. And if I use a ts-criteria, the user would have to hit the button twice in order to achieve the desired sort. I asked on an earlier ticket, if I can start sorting in reverse and I believe you said the answer was no.

[mattiash]

But how can the orderBy statement have any effect at all? What ts-repeat does is that it effectively adds an extra orderBy clause to the end of the ng-repeat expression. The ng-repeat expression is a pipeline where parameters.response generates an array, orderBy rearranges the items in the array in a different order, filter:paramquery removes some entries from the array and then finally the orderBy added angular-tablesort reorders the items again. This means that the operation done by your orderBy filter is nullified by the orderBy added by angular-tablesort.

angular-tablesort can only sort by simple fields, it cannot take a sorting function. I think you are trying to do too much with angular-tablesort and you probably have to write your own custom tablesort routines.