Fixed
Status Update
No update yet.
Comments
[Deleted User] <[Deleted User]>
We're working with the material team to ensure that Navigation matches the new material design guidelines.
fl...@google.com
da...@google.com
ap...@google.com
Hi everyone. What is the progress or official decision on this one?
[Deleted User] <[Deleted User]>
Hey guys, is there any progress on this issue? Can we expect these features to be implemented in the near future?"
da...@google.com
Any update on this?
ma...@marcardar.com
We'll update the bug here when there's updates to post. Suffice it to say, there's still work to do and we're dedicated to getting it done."
je...@gmail.com
Hey guys, any update on this?"
da...@google.com
The two biggest issues and annoyances of this bug for our end users with the new Navigation library and Bottom navigation bar are:
- Changing tab with the bottom bar resets the state and backstack of the previous tab/fragment, so our users are completely losing their navigation history (this is correctly implemented in Google Photos app)
- Pressing back from the root of one tab shows the initial tab/fragment instead of leaving the app"
- Changing tab with the bottom bar resets the state and backstack of the previous tab/fragment, so our users are completely losing their navigation history (this is correctly implemented in Google Photos app)
- Pressing back from the root of one tab shows the initial tab/fragment instead of leaving the app"
[Deleted User] <[Deleted User]>
I'm also facing this issue. Looking forward to the update.
cr...@shou.tv
Facing the same issue here. Any updates?
da...@google.com
I'm also facing this issue, are there any updates?"
pi...@gmail.com
Could we get any public updates on this? We're a bit left in the dark with all of these hotlists that we cannot access. What does it mean, why is Google not more public with something of such a high important as support libraries? Why is Jetpack not open source as well? I might be going on a rant here which no one is gonna end up reading, but it's frustrating to start using the new libraries provided by Google that are supposed to accelerate development. Yet it's so hugely opinionated by the developers at Google and no feedback is being sought from the people actually using it? Why can't we, the people _actually using it_, be the one working on it as well. Why can't we have an open collaboration like Kubernetes or other Google projects? Could Google start opening up a bit more like Microsoft is doing (not that they're all holy)."
ai...@gmail.com
Re #13 - we do read all the comments, rants or not. We'll be updating the bug when there's updates.
Feel free to check out the AndroidX source code and contribution instructions athttps://android.googlesource.com/platform/frameworks/support/+/androidx-master-dev "
Feel free to check out the AndroidX source code and contribution instructions at
Description
Version used: 1.0.0
Room currently supports RxJava and LiveData, but it would be great to also have support for Kotlin's Coroutines.
In a basic implementation this could be achieved with supporting the following types:
- Query: Deferred<T>
- Insert: Job or Deferred<Long>
- Delete: Job or Deferred<Int>
- Update: Job or Deferred<Int>
What could be really awesome though would be implementing support for the `suspend` keyword, as the developer would be able to write just:
```
@Query("SELECT * FROM ITEMS")
suspend fun getItems(): List<Item>
```
I understand this might be tricky to implement on your side though, since a suspend function has got a continuation parameter and that might be an issue with the way Room currently works.