Fixed
Status Update
Comments
il...@google.com <il...@google.com> #2
This is a great idea as it solves one major pain experienced by my developer using Compose.
Another solution idea would be to use "onAppear" modifier to allow each composable have an individual event handler.
For example:
```
Column(
modifier = Modifier
.fillMaxSize()
.onAppear {
viewModel.loadItems()
}
) {
...
}
```
Another solution idea would be to use "onAppear" modifier to allow each composable have an individual event handler.
For example:
```
Column(
modifier = Modifier
.fillMaxSize()
.onAppear {
viewModel.loadItems()
}
) {
...
}
```
jb...@google.com <jb...@google.com>
ap...@google.com <ap...@google.com> #3
As simetrias podem posicionar-se alternadamente face ao número de módulos disponÃveis para o efeito de cada fase
il...@google.com <il...@google.com> #4
This would be really appreciated. Especially when dealing with legacy Android views wrapped in an AndroidView
that require specific methods to be called on certain lifecycle states, like a camera/scanner view for example.
Description
Version used: 2.1.0-alpha03
Devices/Android versions reproduced on:
If you repeat Navigate with URI, the back key does not work.
I'll attach the sample project. Please check below how to reproduction.
1. Tap `MOVE TO A`
2. Tap `MOVE TO B`
3. Tap `MOVE TO D` (Navigate with URI to another nav graph)
4. Press back key.
5. Repeat step 3 and step 4 2 times
6. We can't back to Fragment A.
I think mBackStack is not correct in NavGraphNavigator and NavController.
When step3, NavGraphNavigator#navigate is not called, but NavGraph is added to NavController.mBackStack.
Thanks.