SJOSearchableFetchedResultsController additions #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was using SJOSearchableFetchedResultsController in a scenario where I wanted to display a section index for a table view. So I made some changes to facilitate this. Mainly the ability to override a method in your subclass to specify the
sectionKeyPaththat should be used when constructed new NSFetchedResultsControllers.This worked fine but then I released that the table view section index should not be displayed when the user is searching. So the
newFetchedResultsControllerWithSearch:method takes this into account by ignoring any specifiedsectionKeyPathif the user is searching. This necessitated thesearchIsActiveproperty, which is set to YES when searching begins, and NO when searching is cancelled.I also added the ability to construct a SJOSearchableFetchedResultsController with a managed object context if you want to use SJOSearchableFetchedResultsController without being depending on an SJOStore instance.
So to use a section index in a SJOSearchableFetchedResultsController subclass: