Currently, when a user is on the game info screen and clicks on an image, we need to pass a ready-to-be consumed URL of a clicked image to the image viewer screen. The logic for getting a particular image URL is embedded inside the GameInfoViewModel (like here, here, and here).
It looks quite dirty and a separate use case named something like GetGameImageUrlsUseCase is needed to be created and then GameInfoViewModel refactored to use it.
Currently, when a user is on the game info screen and clicks on an image, we need to pass a ready-to-be consumed URL of a clicked image to the image viewer screen. The logic for getting a particular image URL is embedded inside the
GameInfoViewModel(like here, here, and here).It looks quite dirty and a separate use case named something like
GetGameImageUrlsUseCaseis needed to be created and thenGameInfoViewModelrefactored to use it.