You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 11, 2024. It is now read-only.
In the "Define the ViewModel" step, there is a sentence that reads "As the ViewModel class BusScheduleViewModel needs from is meant to be lifecycle aware, it should be instantiated by an object that can respond to lifecycle events."
Should this instead be? "As the ViewModel class BusScheduleViewModel is meant to be lifecycle aware, it should be instantiated by an object that can respond to lifecycle events."
The text was updated successfully, but these errors were encountered:
If you instantiate it directly in one of your fragments, then your fragment object will have to handle everything all the memory management, which is beyond the scope of what your app's code should do.
and perhaps should be:
If you instantiate it directly in one of your fragments, then your fragment object will have to handle everything, including all the memory management, which is beyond the scope of what your app's code should do.
In the "Define the ViewModel" step, there is a sentence that reads
"As the ViewModel class BusScheduleViewModel needs from is meant to be lifecycle aware, it should be instantiated by an object that can respond to lifecycle events."
Should this instead be?
"As the ViewModel class BusScheduleViewModel is meant to be lifecycle aware, it should be instantiated by an object that can respond to lifecycle events."
The text was updated successfully, but these errors were encountered: