@koke Code looks great! but it's honestly hard to follow the entire hierarchy. (Edit: solvable with some docs!)

Plus, i've got some doubts, such as:

• If you wanna have (any of the standard cells), with a custom accessory indicator, you'd need to just implement another cell, with the style you want. Just wondering if we wanna extend the Row struct to hold more (optional) properties.
• Maybe there's a simpler way (aka less code) to deal with the MockTableView concept. (OCMock?). That'd help eliminate a couple protocols.
• Just wondering about the naming consistency detail. ImmuTable <> WPImmuTableCells (when do we want the WP prefix, and when we don't).

If you wanna have (any of the standard cells), with a custom accessory indicator, you'd need to just implement another cell, with the style you want. Just wondering if we wanna extend the Row struct to hold more (optional) properties.

You'd need to implement another Row, as long as your cell isn't a custom class. As for extending Row, remember that ImmuTableRow is a protocol, not a base class, so any properties added there would still need to be declared in every type that implements the protocol. We wouldn't have less code, and we'd have many more nils floating around.

Just wondering about the naming consistency detail. ImmuTable <> WPImmuTableCells (when do we want the WP prefix, and when we don't)

I added the prefix because they inherit from WPTableViewCell. I'd love to get rid of that dependency and have ImmuTableCells with a sensible default set of cells.

Maybe there's a simpler way (aka less code) to deal with the MockTableView concept. (OCMock?). That'd help eliminate a couple protocols.

Maybe there's a shorter way, but I'm not sure if that'd make it better or more readable

@jleandroperez ready for round two, I'm quite happy with this iteration as everything looks much simpler.

I'm going to keep adding some more documentation, but feel free to start with the code review

I'm done with documentation as well, and reorganised the file to make it more approachable. Please let me know if you find the docs easy to understand.

After this, I'd like to try to move this to a separate library with a bunch of default cells, so it might help with documentation to have a few examples. Also a README separate from the header docs could really help explain what this is and how you're supposed to use it. I added a bit of that at the top of the file, but there's a lot of room for improvement.

@koke i really like what you did with ImmuTable!.

I meant to answer this one, but Github doesn't show the Q anymore:

extension UITableViewController: ViewControllerWithTable { }

Latest implementation looks better than that (less complicated!). There's always room to extend / improve (support for UIViewControllers, ie), but i'm sure ImmuTable can grow as needed / when needed / if needed.

!!