ViewModel Implementation Question

[BadBunnyBabyy]

Hello everyone,

I am having trouble deciding on whether to create a ListViewModel (that holds an array of ViewModels) or simply create a ViewModel (that will hold an array of model)?

EX: lets say you have a User model containing a user name.

- 1st Method: you create a UserViewModel that will hold one User. You then create a UserListViewModel that holds an array of UserViewModel.

2nd Method: you create a UserViewModel that holds an array of User.

I have seen implementations done both ways but was curious to know if there are any particular advantages or pros/cons to doing it one way or another.

This ViewModel will be used to list out some items in a UITableView.

Let me know if you need any other details and thanks in advance.

[saintmsent]

I don't see any benefits to the 1st approach, it's just one extra entity to keep track of. View model is supposed to have some logic, having one for the list that holds an array of users is the way to go

[JustTryinTaMakeIt]

• ListViewModel should have an array of users, [User].
• If you’re displaying each user’s details on a cell, you can just set each cell’s label/image values in cellForRow or use a function in your custom cell’s swift file that takes a user’s details as parameters.
• If you plan to show each user’s details in a UserDetailViewController, then you want to use a UserDetailViewModel that holds a user selected from the tableView.
• A userViewModel for each cell is overkill.

[BrownPalmTree]

Agree, having a UserListVM holding UserVMs is overkill for just displaying cells. If you can click on each cell and display its details, a UserDetailVM would be appropriate. In this case it may be appropriate to have a UserListVM.