rfcs
rfcs copied to clipboard
navigation.continue / next: push but without passing in a route name
:wave:
Given a stack navigator with the following routes:
{
Login,
ConnectGmail,
Loading,
Welcome
}
What
I'm proposing a navigation.continue
or navigation.next
method that will automatically determine the next route in line.
Why
Over the past 6 months we've built different onboarding flows and moving routes around for testing purposes. I have to open up individual files and update to the correct route name.
This isn't the worst thing in the world, but if I could do this at the navigator level it would improve my productivity.
Issues
- sort order may be inconsistent. I would propose a key that would maintain sort order for you:
{
Login: { key: 0, screen: LoginScreen }
}
How
I would be more than happy to implement this.
Thank you!