Day 54. Voyager issue

What I did:

Today, I fixed a small UI issue on the ArticleScreen. Afterward, I implemented logic to open the article feed for the selected screen. I noticed that when opening several tags in a row, only the tag was displayed on the screen.

After debugging, I found that the instance of Voyger's ScreenModel was identical for every open screen. I use the Koin factory method to create instances and expect that each time I open a new screen, a new ScreenModel will be created for it. However, something goes wrong.

My initial thought was that I might have sent incorrect parameters in koinViewModel() and Voyager didn't recognize the parameters as being different. I converted the models to data classes, which should have prevented this behavior. However, this didn't resolve the issue. I found a solution in the Voyager sample with Koin integration:

class KoinScreen : Screen {

    override val key: ScreenKey = uniqueScreenKey

    @Composable
    override fun Content() {
        val screenModel = getScreenModel<KoinScreenModel>()

        ListContent(screenModel.items)
    }
}

I couldn't find the exact code where the key was used, but I believe defining the scope correctly is crucial for this class. By default, the key is a string related to the class name. As a result, If I open several identical screens, they will share the same SreenModel. This line of the code prevents this behavior: override val key: ScreenKey = uniqueScreenKey. Finally, I added logic to fetch user data by ID.

What I will do: