Replacing CoroutineScopes with viewModelScope #58
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on #22
Problem
Using CoroutineScope instead of using viewModelScope inside viewModel.
Solution
The replacement has been made based on the following description;
Using a viewModelScope within a ViewModel is a more convenient, safer, and easier way to create and manage a CoroutineScope. viewModelScope automatically cancels processes and ensures that they are run on the correct thread, so it's the more preferred approach overall.
Test
Tested whole application features on Google Pixel 3.