v4 replace behaves different to v3?

[compojoom]

The normal navigation between my scenes is:
A->B->C

on scene B, you can press and add button and this would send you to scene D. When you click save, then you are sent to scene C. Now clicking the back button on scene C shouldn't send you back to scene D, but to B.
A->B->D->C
back is
C->B->A

I was able to achieve this with v3 by using type replace. Now on v4 if I use Actions.replace('D') -> then all the scenes in the stack are replaced with scene D and not just the last one. Is there a way to just replace the last one?

[aksonov]

Looks like it is the problem of React Navigation:
react-navigation/react-navigation#774

If you could find solution how to do 'replace' correctly with react-navigation I could implement it with RNRF.

[aksonov]

I have one idea - do Actions.pop and Actions.push for 'replace'. I will try to implement this.

[compojoom]

I tried pop and then push, but I'm not sure if it was my components or what, but I was running in a "max execution callstack" error.

[aksonov]

OK, I will try for Example.

[aksonov]

@compojoom Could you check latest master?

[itinance]

@aksonov Have you unpublished beta11 and beta12? We got an empty folder after "npm install" of an other library and while reinstalling neither beta11 nor beta12 can be found on npm.

[aksonov]

Have you tried 4.0.0-beta.12 ?

[itinance]

ooops.... thx! don't know how it could work without the dot yesterday (or the dev was on del-key)^^
However, can you tell pls the roadmap for 4.0.0 - non-beta?

[aksonov]

It would be a little bit strange to remove beta if react-navigation is still in beta, what do you think? I would like to remove beta once we will have one week without bugs. But how to deal with react-navigation bugs (like bugs with tab bar)

…

On 25 Jul 2017, at 11:19, Hagen Hübel ***@***.***> wrote: ooops.... thx! don't know how it could work without the dot yesterday (or the dev was on del-key)^^ However, can you tell pls the roadmap for 4.0.0 - non-beta? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2102 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABQpcc6ybHio2zuYBmgva3xyn0neCaZ_ks5sRbMNgaJpZM4OhNE1>.

[itinance]

yes, wouldn't think that. thats why i was asking :) with git remote show origin and git branch i could see a lot of release-branches but not these both. was a bit confusing.
Originally I ran into this npm-issue that removes other dependencies sometimes and lost RNRF and all this got followed up with lots of side-issues... It's clear now :)

[aksonov]

Should be fixed with 4.0.0-beta.14

[aksonov]

I've just added ActionConst.POP_AND_PUSH action for this (previous REPLACE could be useful to replace root scene)