在VIPER体系结构中，NSFetchedResultsController放在哪里?

问题描述：

在 VIPER 中，与MVC不同，角色和位置并非如此明确为NSFetchedResultsController定义.

In VIPER, unlike the MVC, the role and place not so clearly defined for NSFetchedResultsController.

将其放置在交互器上是否正确?

Is it right to place it on the interactor?

答

根据本文交互者不应该知道如何持久化实体.

According to this article interactor should not know how to persist the entities.

VIPER和使用NSFetchResultController的体系结构是不同的方法. VIPER中的NSFetchResultController没有合适的位置.

VIPER and the architecture that uses NSFetchResultController are different approaches. There is no right place for NSFetchResultController in VIPER.

VIPER非常适合大型应用程序，因为它提供了很好隔离的体系结构层.

VIPER is good for big application as it provides architecture layers that are isolated well.

NSFetchResultController对于较小的应用程序非常有用，因为它有助于更快地开发.

NSFetchResultController is good for smaller application as it helps to develop faster.