My data consists of a table with 100 rows, each representing a complex object that is an instance of a specific type. User interactions trigger operations on these objects individually, with each row having unique operations independent of the others.
$scope.list = [] // List of instances created from factory functionEach object maintains its state through its own instance with getters, setters, and row-specific logic. With one controller for the entire table and 100 individual instances, I am considering implementing row-level controllers.
By using row-level controllers, there would be a total of 101 controllers (100 row level, 1 table level) for 100 rendered objects in the table, allowing me to handle view-related logic for each object within the respective controller rather than in the factory instance.
I am concerned about performance implications and whether this pattern is optimal. Would using controllers inside ng-repeat be advisable? Your feedback on this approach would be appreciated.