Pop back to specific scene

[cgreening]

Anyone know how to pop back several scenes to a particular scene?

e.g.

<Scene key="root" hideNavBar={true}>
    <Scene key="Test1"/>
    <Scene key="Test2"/>
    <Scene key="Test3"/>
    <Scene key="Test4"/>
</Scene>

If I'm on Test4 how can I pop back to Test2?

[aksonov]

It is not supported within v3 right now, PR will be welcome.

[aksonov]

@cgreening Have you tried Actions.pop();Actions.pop() ?

[cgreening]

We've got a workaround with a custom reducer where we modify the state to
get it back to the scene we want.

Will try and turn that into a pr.

This does look pretty horrible though as every scene is animated off in
rapid succession. I believe this might be an issue with the underlying
navigation component. I think it needs a bit more work to bring it into
line with the standard native iOS uinavigationcontroller.

On Thursday, 31 March 2016, Pavlo Aksonov notifications@github.com wrote:

@cgreening https://github.com/cgreening Have you tried
Actions.pop();Actions.pop() ?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#419 (comment)

[Mbompr]

Hi @cgreening apparently you did not have time to turn it into a PR. By any chance, could share with us your custom reducer, I am facing the same problem.

[cgreening]

customRouterReducer.js:

import {Reducer} from 'react-native-router-flux';

const reducerCreate = params=>{
    const defaultReducer = Reducer(params);
    return (state, action)=>{
        if(action.type == 'BODGE') {
          if(state.children.length > 1) {
            state = Object.assign({}, state, {index: 0, children : state.children.slice(0,1)});
           }
        } else {
          state = defaultReducer(state, action);
        }
        return state;
    };
};

export default  reducerCreate;

And then in your setup do:

import customRouterReducer from './customRouterReducer'
import {Actions, Scene, Modal, Router} from 'react-native-router-flux'

const ConnectedRouter = connect()(Router);

<ConnectedRouter scenes={scenes} createReducer={customRouterReducer}/>

Then send actions with the type "BODGE" to pop back to the first scene.

[esutton]

@cgreening Thank you!

Dumb question: Can you please give example on how to send action with type "BODGE" ?

I am a Javascript/react newbie. All I have been using are Actions fiuctions like:

Actions.pop()

Actions['MySceneKey']({
      myObject: myObjectSelected,
      title: "Hello",
});

[cgreening]

In a connected component you should be able to do:

this.props.dispatch({type: 'BODGE'});

[sym900728]

I write in the my component with the

this.props.dispatch({type: 'BODGE'})

It's not useable.

[benjamincarp]

Actions.js mentions popTo in several places, which I assume would do what we're looking for here but I didn't have any luck trying to actually use it and I find the layout of this code pretty hard to read so I didn't dig in too far.

In my case, I need to pop to the root level so I could just use a replace action for now. I would prefer for it to be a pop to the correct level though in case we ever add a level below the current root.

[JosephDev]

same here. Actions.ROUTE_NAME({type: ActionConst.RESET}); occur errors blow.

I use ActionConst.BACK instead.

Please mention if I use it as wrong way. thanks,

[MattyK14]

+1

[highbass]

I get the exact same error as @JosephDev when trying to use POP_TO, however, RESET works fine for me unfortunately it doesn't solve my requirements.

edit:

Well looks like i was using POP_TO incorrectly... I think documentation requires some better explanation but this ticket showed how its supposed to work.

#1594

[redwind]

@cgreening: thanks for your hack
@sym900728 : if this still help for you, it work for me by call
Actions.callback({ type: 'BODGE' })