Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a root coordinator per legacy screen flows #3597

Open
1 of 19 tasks
SBiOSoftWhare opened this issue Aug 31, 2020 · 0 comments
Open
1 of 19 tasks

Create a root coordinator per legacy screen flows #3597

SBiOSoftWhare opened this issue Aug 31, 2020 · 0 comments

Comments

@SBiOSoftWhare
Copy link
Contributor

SBiOSoftWhare commented Aug 31, 2020

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:

  • 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
  • room settings
  • authentication
    ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
UI Navigation
  
To do
Development

No branches or pull requests

2 participants