can I not do this? ```fun NavHostController.navig...

# compose

[oday]

can I not do this?

fun NavHostController.navigateBookDetail(
    bookId: Long,
    bookTitle: String
) {
    setState("bookId", bookId)
    setState("bookTitle", bookTitle)
    navigate(Routes.Slave.BookDetail.path)
}

composable(Routes.BookDetail.path) {
        val bookId = navController.getBookIdStateFromState()
        val bookTitle = navController.getBookTitleFromState()


            BookDetailScreen(
                bookId = bookId,
                bookTitle = bookTitle,
            )
    }

@HiltViewModel
class BookDetailViewModel @Inject constructor(
    private val snippetRepository: SnippetRepository,
    savedStateHandle: SavedStateHandle
) : ViewModel() {

    init {
        val bookid = savedStateHandle.get<Long>("bookId")
        val bookTitle = savedStateHandle.get<String>("bookTitle")
    }
}

I'm getting back null in the viewmodel, the only way this would work if I have BookDetail/{bookId}/{bookTitle} AND I set the arguments as navArgs in the composable

but can I not do the above and still get back the values in the statehandle? I don't want to send them in the "normal" way for example

[Ian Lake]

All arguments need to be in the route, that's kind of the whole point

[oday]

yea.. i know..just insisting on a broken solution, sunken cost, ok thanks Ian

[Ian Lake]

Feels weird to be passing a book title at all - I'd assume your actual data source for book data (a repository layer, whether that is hooked into a local database or just a cache for data) would look up the book title and other details given the ID

[oday]

true but I want the title to sit in the top bar, I assume it would be faster to get it there through nav args than to have to wait for a query

but yea sure makes sense, I will actually go for that instead