| Elaine Chien | 719e2d8 | 2023-07-27 18:00:19 | [diff] [blame] | 1 | # Views MVC Developer Guide |
| 2 | |
| 3 | ## Components and Concepts |
| 4 | |
| 5 | ### Model: |
| 6 | * Contains data related to the display of the view |
| 7 | * Treat backend service as separate models |
| Elaine Chien | 7894271 | 2023-11-03 17:17:39 | [diff] [blame] | 8 | * Gets updated by the view controller |
| Elaine Chien | 719e2d8 | 2023-07-27 18:00:19 | [diff] [blame] | 9 | |
| 10 | ### View: |
| 11 | * Presentation of UI |
| 12 | * Receives and handles events from the user that don’t require model data |
| 13 | * Is called into by the View Controller and does not interact with the model |
| 14 | * The view should end up being pretty simple |
| 15 | |
| 16 | ### Controller: |
| 17 | We break up the traditional Controller into the Coordinator and View Controller. More complicated features where the View Controller gets unruly can also further split out a mediator object (Reach out to the views team for more details if your team would like to explore that option) |
| 18 | |
| 19 | #### Coordinator: |
| 20 | * Public API of the component |
| 21 | * In charge of when features become active or inactive |
| 22 | * Owned by the coordinator of it’s parent component |
| Elaine Chien |
|
