Skip to content
New issue

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

Context as to whether a navigation was back or not #926

Closed
maknz opened this issue Oct 13, 2015 · 3 comments
Closed

Context as to whether a navigation was back or not #926

maknz opened this issue Oct 13, 2015 · 3 comments
Assignees
Milestone

Comments

@maknz
Copy link

maknz commented Oct 13, 2015

It would be useful to be able to find out if a navigation was back or just a regular forward navigate, something like isBackNavigation: true.

It would also be useful to provide context for the back navigation, separate from the navigation context. The navigation context must persist when using goBack, as the page you're going back to has to know how it was navigated to in the first place. However, it would be useful to be able to pass some separate context for the back navigation -- say, a child view that was responsible for editing a record from a parent view, passing back that record to the parent when saved (it would get back to the parent via goBack).

@N3ll N3ll added this to the 1.5 (Under Review) milestone Oct 13, 2015
@nsndeck nsndeck self-assigned this Oct 14, 2015
nsndeck pushed a commit that referenced this issue Oct 23, 2015
@nsndeck nsndeck added done and removed in progress labels Oct 23, 2015
@nsndeck
Copy link

nsndeck commented Oct 23, 2015

Issue fixed with commit #975.

@nsndeck nsndeck closed this as completed Oct 23, 2015
@maknz
Copy link
Author

maknz commented Dec 22, 2015

@nsndeck does this fix allow for us to pass navigation context with goBack()?

@lock
Copy link

lock bot commented Aug 30, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Aug 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants