-
Notifications
You must be signed in to change notification settings - Fork 47
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
Compass 6.0 Roadmap #54
Comments
All the proposed features make sense for me 👍 |
I support this! |
I was about to raise an issue to make Navigator a class, but then read this :) +1 definitely to making it an instance. Can we go one further and make it a protocol as well i.e. |
How's the progress on this going? Really excited to see version 6. |
As Swift 4.1 release, some codes are deprecated. Can't wait for the version 6 of this great library :) How is the progress? |
We will convert Compass to be in Swift 4 soon. This is not really big changes, but we can take this advantage to do some refactoring. Some are breaking changes. My proposals are
scheme
andRouter
into it. An app usually does not need manyNavigator
, and use can just set it as the current one. This also promotes the use ofRouter
Navigator
andRouter
seem to confuse users. Like we declareRouter
, but also configureNavigator.routes
. The aboveNavigator instance
will make the composition clearNavigator -> Router -> Routable
currentController
, some likepreLogin
prefers to switch rootViewControllerErrorRoutable
, as we can handle viatry catch
withnavigate
functionWhat do you think @hyperoslo/ios ?
The text was updated successfully, but these errors were encountered: