|
|
|
|
13
|
## Why Rebuild react-native-navigation?
|
13
|
## Why Rebuild react-native-navigation?
|
14
|
|
14
|
|
15
|
### A New & Improved Core Architecture
|
15
|
### A New & Improved Core Architecture
|
16
|
-react-native-navigation has a few issues which are unsolvable in its current architecture. These issues stem from the same problem: you cannot specify on which screen you wish to make an action. Whenever you want to push a screen, show a modal or any other action, the action defaults to originate from your current screen. In most cases this is fine, but becoms problematic in specific edge cases. For example: <br>
|
|
|
|
|
16
|
+react-native-navigation has a few issues which are unsolvable in its current architecture. These issues stem from the same problem: you cannot specify on which screen you wish to make an action. Whenever you want to push a screen, show a modal or any other action, the action defaults to originate from your current screen. In most cases this is fine, but becomes problematic in specific edge cases. For example: <br>
|
17
|
* What if you want to update your navbar icons and the user pops the screen? Your icons might update on the wrong screen.
|
17
|
* What if you want to update your navbar icons and the user pops the screen? Your icons might update on the wrong screen.
|
18
|
* What if you want to push a screen as a result of a redux action?
|
18
|
* What if you want to push a screen as a result of a redux action?
|
19
|
|
19
|
|