element-hq / element-hq/element-ios

Create a root coordinator per legacy screen flows

未关闭
#3,597 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
A-Developer-Experience A-Navigation
主要语言
Swift
星标
1.8k
派生
544
PR 合并指标
PR 指标待抓取

描述

At the beginning we can create several root coordinators to handle screen flows in ObjC. Navigation between detail screens in these flows can be called from view controllers directly but the root view controllers should delegate navigation to the coordinator. We can create a root coordinator for:
- [x] split view
- [ ] tab bar: `TabBarCoordinator` exists,
- [ ] continue to migrate navigation code from `TabBarController` to `TabBarCoordinator`
- [ ] remove navigation to authentication, settings and so on when they are migrated to coordinator. They should be managed from other places.
- [ ] Unified search
- [ ] RoomViewController presentation (`showRoomDetails`)
- [ ] Contact details (`showContactDetails`)
- [ ] Show group detail (`showGroupDetails`)
- [ ] Show settings
- [ ] every root view controller from the tab bar
- [ ] home
- [ ] favorites
- [ ] people
- [ ] rooms
- [ ] groups
- [ ] settings
- [ ] room, look at Tchap [RoomCoordinator](https://github.com/dinsic-pim/tchap-ios/blob/develop/Tchap/Modules/Room/RoomCoordinator.swift)
- [ ] room settings
- [ ] authentication
...

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。