-
Notifications
You must be signed in to change notification settings - Fork 73
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
BackHandler Composable #324
Comments
I'm not sure we can do this at either level of abstraction we provide. Definitely not Redwood but even with Treehouse it seems like a stretch. We know nothing about screens, navigation, or, in the case of Android, the platform back-handling third-party library you need to use. |
Good call. Probably this goes in the Cash layer on top. |
We may be able to pull it off in Treehouse at some point, but yeah the question is whether we want to impose the necessary bits to wire this up. Maybe a sample to show how it's wired? |
|
In Compose: BackHandler(true /* or state derived */) {
// must handle
} |
I've since come around to this being supported at the Redwood layer because it relies on things like #1116 which previously did not exist as a concept. |
Lets hook up something like Compose UI’s BackHandler.
The text was updated successfully, but these errors were encountered: