Swift中TableViewController的MVC架构疑问：单元格与数据源合规性
Great question—let’s unpack this clearly since MVC can feel a bit ambiguous when working with UIKit’s table view components.
1. Is a Table View Cell part of the View layer?
Absolutely. UITableViewCell is a core UIKit view class, so it falls squarely in the View layer of MVC. Its sole job is to present data visually: configure labels, images, layout, and handle UI-specific states like selection or highlighting. It should never contain business logic, data processing, or direct references to your model classes (ideally, it just receives prepped data to display).
2. Does using a standalone model class as the data source follow MVC rules?
100%—this is actually the recommended MVC practice. The Model layer’s purpose is to encapsulate your app’s data and business logic. A standalone model (like TodoItem or UserProfile) keeps data logic separate from both views and controllers.
Here’s how it fits cleanly into MVC:
- Your Model holds raw data and any logic tied to it (e.g., validating a todo item’s due date)
- Your Controller (like
UITableViewController) fetches or requests this model data, then passes it to the Table View Cell for display - The View (Cell) never interacts directly with the Model—this strict separation is the heart of MVC design.
3. Is UITableViewController a mix of View and Controller?
This is a common point of confusion, but the short answer is: No, it’s still a Controller-layer component.
Apple designed UITableViewController to simplify managing a UITableView—it automatically holds a reference to the table view and conforms to its data source/delegate protocols. But its core role remains that of a Controller:
- It mediates between your Model data and the Table View/Cell
- It handles user interactions (e.g., tapping a cell, pulling to refresh)
- It manages the table view’s state (reloading data, handling row insertion/deletion)
That said, you can make it even cleaner by extracting data source/delegate logic into a separate class (e.g., TodoListDataSource) to keep your view controller focused solely on coordination. But even without that, UITableViewController doesn’t cross into View-layer territory—it never handles rendering UI (that’s the cell’s job) or business logic (that’s the model’s job).
内容的提问来源于stack exchange，提问作者user9767538
