Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A new Android Pull Request #2

Open
wants to merge 3 commits into
base: feature/android-dummy-app
Choose a base branch
from

Conversation

Nerdy-Things
Copy link
Owner

No description provided.

override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)

setContent {
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

18 : ViewModel should not be instantiated directly in the activity . ViewModel should be retrieved via ViewModel Provider to correctly handle lifecycle states and to share data between different components such as activities and fragments .

Surface(
modifier = Modifier.fillMaxSize(),
color = MaterialTheme.colorScheme.background
) {
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

24 : Could potentially crash due to Network On MainThread Exception . The :: load State method usually loads data from network or database which cannot be performed on Main Thread , so it should be executed within a coroutine scope .

modifier = Modifier.fillMaxSize(),
color = Color(0xFFFFFFFF)
) {
MainScreen(state, viewModel::loadState, ::openNerdyThings)
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

32 : Activity context being passed to the ViewModel in the prepare Text (this ) method . It might cause memory leaks if not handled properly . ViewModel should never have a reference to an activity , use application context instead .

import kotlinx.coroutines.flow.MutableStateFlow
import kotlinx.coroutines.launch

@OptIn(DelicateCoroutinesApi::class)
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

9 : " UserProfile Repository ()" instance is created directly in the ViewModel . Should use dependency injection for better test ability and maintain ability .

GlobalScope.launch {
uiState.emit(UiState.Loading)
try {
val userProfile = retrofitService.service.getUserProfile().userProfile
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

30 - 34 : Pot entially leaking the context if it 's an Activity context . Context should be used carefully and not held longer than necessary to prevent memory leaks . In this case , context might be held longer than necessary through the label Provider .

} catch (e: Exception) {
uiState.emit(UiState.Error)
}
}
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

35 : Global Scope used . In case the ViewModel is destroyed before this coroutine finishes , it can lead to memory leaks as it will keep the ViewModel instance alive until the coroutine completed .


sealed class UiState {
data object Loading : UiState()

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

40 : Any error in the network call will only emit " Ui State .Error ", no debugging information or differentiation between types of errors .

}

companion object {
lateinit var labelProvider: (UserProfile) -> String
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

47 : label Provider is defined in a companion object , which is essentially a static field that holds an instance to a function that uses context . If the context is an Activity , this can lead to serious memory leaks .

companion object {
lateinit var labelProvider: (UserProfile) -> String
}
}
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

49 : No safe call or null check before using label Provider which will throw a null exception if it is not initialized before calling load State ().

@Nerdy-Things Nerdy-Things reopened this Mar 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants