Support for descending sort when use grouping

[bronenos]

Made public just a boolean, whether or not use the grouping.
If true, then use the first sorter as grouping path, automatically.

[isaacroldan]

I understand the issue, but i don't think you need to change all that stuff. The information you need is already passed in the methods, no need to change everything, just the sortSections method:

private func sortSections() {
    guard let sortd =  request.sortDescriptors.first else { return }
    let comparator: NSComparisonResult = sortd.ascending ? .OrderedAscending : .OrderedDescending
    sections.sortInPlace { $0.keyPath.localizedCaseInsensitiveCompare($1.keyPath) == comparator }
}

If you don't want to group, don't pass a sectionKeyPath
This is how NSFetchedResultsController works, and i think is better to try to keep a similar API.

EDIT: If travis fails, review the tests :)

[bronenos]

Well, I see, I lost the local request with all info I need, yes.
And the task could be completed like the way above.

But, by the way, what for do you need to store sectionKeyPath in RRC, if there's no usage of this property inside RRC? And why do programmer have to provide the similar keyPath and first sorter, if it could be simplified? Or the viewpoint is just to be similar with CoreData's API?

[polqf]

As it is a NSFetchedResultsController-like Library, we want our API to be as similar as possible to it.
An iOS Developer is used to it, so the goal is to facilitate the migration from CoreData to Realm without having to know a lot about the library itself, while we provide a good implementation.

[bronenos]

Good point. Okay, I got it.
Well, who may apply the changes above? You or me?

[isaacroldan]

Feel free to do it :)

[isaacroldan]

👍

[polqf]

sections.sortInPlace { $0.keyPath.localizedCaseInsensitiveCompare($1.keyPath) == sortd.ascending } ?

[bronenos]

comparator is NSComparisonResult but sortd.ascending is Bool

[polqf]

My fault

[polqf]

👍

[isaacroldan]

Thanks @bronenos

[polqf]

👏