Last active
February 5, 2017 19:27
-
-
Save dcow/c5365aec81ca0dadf012c1ad5a847bdb to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Flow 0.12 -> 1.0 migration guide | |
| StateParceler -> KeyParceler | |
| Flow.Dispatcher -> Dispatcher | |
| flowDelegate.onNewIntent(Intent) -> Flow.onNewIntent(Intent, Activity) | |
| flowDelegate.onResume()[other lifecycle] -> InternalLifecycleIntegration/InternalContextWrapper | |
| Path -> "key" ... (not full story, keys are trivial now) | |
| Flow.Traversal -> Traversal | |
| Flow.TraversalCallback -> TraversalCallback | |
| MortarScoper via FlowServicves | |
| PathContainer -> KeyChanger | |
| PathContinerView -> FlowContainerView (you make your own but get the key changing stuff out save for transition hooks to animate things) | |
| Flow installation is prepped when the baseContext is attached (because it needs to wrap it) but installation only actually happens after the activity is created. Anything in onCreate that was flow related moves to onPostCreate. | |
| -- All dependencies/scopes need to be available at the point that flow wrapps the base context instead of bootstrapped onCreate. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The actual Flow installation happens when the
Application:ActivityLifecycleCallbacksattaches the internal lifecycle integration fragment to the activity inonActivityCreated(), which means that theFlowinstance only starts to exist afteronCreate()but beforeonPostCreate().