Is there a reason that RBQFetchedResultsController doesn't allow injection of a realm path instead of generating it's own from cache names? Since I have another class that manages the creation of a realm with a custom path and dealing with realm transactions this would be a helpful way to initialize an instance of RBQFetchedResultsController. Would adding this initializer cause any issues with how the class is currently implemented? Thanks for the insight in advance!
Is there a reason that RBQFetchedResultsController doesn't allow injection of a realm path instead of generating it's own from cache names? Since I have another class that manages the creation of a realm with a custom path and dealing with realm transactions this would be a helpful way to initialize an instance of RBQFetchedResultsController. Would adding this initializer cause any issues with how the class is currently implemented? Thanks for the insight in advance!