We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suppose my app has the following 3 screens
Main (TabA, TabB) DetailA DetailB
click on item in TabA -> DetailA, click on item in TabB -> DetailB
Now I can set history (Main, DetailB), ideally I should also set the tab in Main to TabB to make UI consistent. But that seems not possible.
My scenario is user clicking on a notification to open the app.
The text was updated successfully, but these errors were encountered:
Initial parameters should be part of the Key.
Sorry, something went wrong.
Got it. It could work. But making two different keys (or more) out of a single tabbed screen is a little uncomfortable to me.
I tend to just add different parameters to the same key.
No branches or pull requests
Suppose my app has the following 3 screens
Main (TabA, TabB)
DetailA
DetailB
click on item in TabA -> DetailA, click on item in TabB -> DetailB
Now I can set history (Main, DetailB), ideally I should also set the tab in Main to TabB to make UI
consistent. But that seems not possible.
My scenario is user clicking on a notification to open the app.
The text was updated successfully, but these errors were encountered: