wealthfront / magellan

The simplest navigation library for Android.

wealthfront/magellan Issues

Investigate adopting resource prefixes and/or private resources
Updated 7 months ago
Use androidx.activity.Activity rather than android.app.Activity
Updated a year ago
Expose callback for completed transitions
Closed 2 years ago1
Scope currentScreen() method to Navigator it is called on
Updated 2 years ago
Support currentNavigable in LegacyJourney and LegacyExpedition
Updated 2 years ago
Magellan vs Jetpack Navigation Safeargs
Updated 3 years ago2
Call Screen.transitionFinished() on root screen
Closed 3 years ago
Add nullability annotations for better Kotlin support
Updated 3 years ago
Include view names in multiple views error
Updated 3 years ago
Separate calls to onCreateView/onShow in ScreenGroups
Closed 3 years ago1
Case for onPopped/onDestroy
Updated 3 years ago1
Allow adding a screen to a ScreenGroup after init
Closed 3 years ago1
Consider adding support for lifecycle components
Updated 3 years ago
Create a LinearScreenGroup
Updated 3 years ago
Add support for pluggable screen "components"
Closed 3 years ago1
Consider making navigation asynchronous
Updated 3 years ago
Forbid duplicate pointers to a screen in the backstack
Closed 3 years ago1
Improve testing support
Closed 3 years ago1
Create a Step-based wrapper Screen in magellan-legacy
Updated 3 years ago
Add back javadocs or kdocs
Updated 3 years ago
Dialog is set to null before it gets dismissed
Updated 3 years ago
Consider allowing nested navigation with Magellan Navigators
Closed 3 years ago1
ScreenGroup should call save() in addition to onSave()
Closed 3 years ago1
Exception while using the navigator.goBack()
Closed 3 years ago2
Attempt to invoke virtual method 'void com.wealthfront.magellan.ScreenContainer.setInterceptTouchEvents(boolean)' on a null object reference
Closed 4 years ago2
State of library
Closed 5 years ago1
Equality checking when navigating back
Updated 5 years ago2
Tabs screen with more than 2 screen bug
Closed 5 years ago1
Question: when calling Navigator.goTo() the previous view is destroyed. How can I return to that view when calling Navigator.goBack
Closed 5 years ago1
On navigator.
Closed 6 years ago
Consider adding a cancel method to transitions
Updated 6 years ago
Create SharedElement-style Transition
Updated 6 years ago8
Support navigation that doesn't destroy old screen's view
Updated 6 years ago
Consider making screen.showDialog() accessible from the view
Closed 6 years ago1
Allow more customization of the action bar
Updated 6 years ago1
Add support for circular reveal with coordinates
Updated 6 years ago
Create fake/dummy implementation of screen and/or navigator
Updated 6 years ago
Rename SingleActivity to something like SimpleSingleActivity
Updated 6 years ago
Issues accessing ViewModel and observing LiveData in views
Updated 6 years ago5
Multiple activites
Closed 6 years ago2
onRequestPermissionResult and onActivityResult support
Updated 6 years ago4
Support for autodispose
Closed 6 years ago2
Error: Only TabItem instances can added to TabLayout (Kotlin)
Updated 7 years ago1
Testing with espresso
Closed 7 years ago4
Using data binding
Closed 7 years ago2
Question: any plans to have a some kind of a PreferenceScreen?
Closed 7 years ago2
onResume and onPause use case
Closed 7 years ago2
Restarting or recreating an activity with dagger issue
Updated 7 years ago1
Actionbar design discussions
Closed 7 years ago1
Leak canary integration sample
Closed 7 years ago