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
Since this seems to have become the most up to date modern android development sample, I think it would be a great idea to have it include at least one example of how one-time UI events should be handled. I am referring to this section https://developer.android.com/topic/architecture/ui-layer/events#views_3 from the documentation, which pushes people away from LiveData, Channel and other such approaches. To further assist devs into taking this approach instead, this sample could serve as an example of how to this right in a fully fledged app.
Describe the solution
Particularly it'd be interesting to see handling one-time events like showing something to the screen once and then clearing the state as it's handled, or even more so, consuming events that require the app to navigate somewhere else. In my opinion these are two super common use cases while creating apps that would be great to exist inside the most up-to-date app example provided officially from Google.
Additional context
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Describe the problem
Since this seems to have become the most up to date modern android development sample, I think it would be a great idea to have it include at least one example of how one-time UI events should be handled. I am referring to this section https://developer.android.com/topic/architecture/ui-layer/events#views_3 from the documentation, which pushes people away from LiveData, Channel and other such approaches. To further assist devs into taking this approach instead, this sample could serve as an example of how to this right in a fully fledged app.
Describe the solution
Particularly it'd be interesting to see handling one-time events like showing something to the screen once and then clearing the state as it's handled, or even more so, consuming events that require the app to navigate somewhere else. In my opinion these are two super common use cases while creating apps that would be great to exist inside the most up-to-date app example provided officially from Google.
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: