Back navigation with arguments

[Smoothie1-ini]

Is it possible with Voyager to navigate back with arguments like navigating forward?

[0xZhangKe]

Hello, can you find any solution for this case?

[kodysharma]

you can pass one additional parameter to take output.

[Syer10]

Feel free to watch this issue #39

[CompileConnected]

I suggest using how fragment in android is instantiate. Which is i already tested and works on private project.
so for this example.
we will Have ScreenA Passing data to Screen B.
And ScreenB passing result to ScreenA
you have Screen A and Screen B, and you need result from Screen B to Screen A.

@Serializable
data class DataAToB(
    val name: String,
    val surename: String,
 )

val DataAToBSaver = Saver<DataAToB?, String>(
    save = {
        if (it != null) {
            Json.encodeToString(serializer(), it)
        } else {
            ""
        }
    },
    restore = {
        if (it.isNotEmpty()) {
            Json.decodeFromString(it)
        } else {
            null
        }
    }
)



class ScreenB : Screen {
    companion object {
        fun newInstance(data: DataAToB): ScreenB {
            val screen = ScreenB()
            screen._data = data
            return screen
        }
    }

    override val key: ScreenKey
        get() = uniqueScreenKey

    private var _data: DataAToB = null

    @Composable
    override fun Content() {
          var savableDataAToB by rememberSaveable(stateSaver = DataAToBSaver) {
            mutableStateOf(null)
        }
        
       //this is for handling when application in background
           if (_data != null) {
            savableDataAToB = _data
           //do something
        } else if (savableDataAToB != null) {
            //do something
        }
       // so you do something to pass result from B to A
               val navigator = LocalNavigator.currentOrThrow
           navigator.pop()
           navigator.replace(ScreenA(Result))
    }
}
 
 
 class ScreenA() : Screen {
    companion object {
        fun newInstance(data: ResultB): ScreenA {
            val screen = ScreenA()
            screen._data = data
            return screen
        }
    }

    override val key: ScreenKey
        get() = uniqueScreenKey

    private var _data: ResultB = null

    @Composable
    override fun Content() {
          // the rest of code ...
       
    }
}
    

[CompileConnected]

@Syer10
to be honest i don't like how it pass the data using the screenmodel.
and bloc pattern is just mess of spaghetti code they promote as clean.

hope this help you all, @Smoothie1-ini @0xZhangKe @Syer10

[DevSrSouza]

If you are looking for a result API, you can follow this example extension here: #128 (comment)

Looking forward to any contribution to a more type safe result extension.