Hedger Wang

@sahrens yes. Below is the pseudo codes to demonstrate how I think the transition of stack should be handled and rendered for the view. ``` const MyNavigationView = React.createClass({ getInitialState()...

The question is about stacks transition. Specifically, a data type that contains the information the the two stacks (before and after) that are transitioning from one to another.

There can be unlimited type of animations, but we should try to provide the standard way to represent the data needed for transition. For instance, a AnimatedNavigationBar wants to react...

@aksonov : do you have a minimum repro? perhaps you can reproduce this with the modified module.exports = NavigationCardStackExample?

@aksonov : Does `replace` mean replace current `navigationState` with another one? For that case, you could probably change the reducer at `NavigationCardStackExample` to this: ``` function createReducer(initialState) { return (currentState,...

I see. I think you could start with adding `replace` to `NavigationStateUtils` then change the reducer to the following: ``` function createReducer(initialState) { return (currentState, action) => { switch (action.type)...

Do you want the replaces navigation state to go way with animation or just be removed immediately? What kind of warning that you were getting? Could you please share a...

@rogchap, We're working on porting the current Navigator API to the **new** LegacyNavigator component. Some of the default `configureScene` settings (e.g. `NavigatorSceneConfigs.FloatFromBottom`, `NavigatorSceneConfigs.FloatFromRight`) will be supported. Below is the snippet...

@ericvicenti : I'll do that once my latest diff lands.

@5amfung You can disable the gesture by doing this. ``` ```