Frontmatter
| id | 2354 |
| title | calendar.view.MainContainer: add a view model |
| state | Closed |
| labels | enhancement |
| assignees | tobiu |
| createdAt | Jun 13, 2021, 4:48 PM |
| updatedAt | Jun 13, 2021, 4:57 PM |
| githubUrl | https://github.com/neomjs/neo/issues/2354 |
| author | tobiu |
| commentsCount | 0 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Jun 13, 2021, 4:57 PM |
Normally I don't use VMs for component creation.
The calendar is more like an app though, so it does make sense here:
We need to pass less configs to sub views and this enables you to use sub-views on their own (adding the VM).
Another benefit is that you can override "global" VM props with adding a VM for a child view. E.g. in case you want to use a different time format only inside the week view or only allow editing events there.