Fixed
Status Update
No update yet.
Comments
an...@backx.org
il...@google.com
> We accept pull requests! :)
Is there a public repo somewhere? I don't see any obvious repo for it inhttps://android.googlesource.com , and it doesn't seem to be inside https://android.googlesource.com/platform/frameworks/support .
Room supports final fields (yay!), which probably will suffice for many people with respect to this feature request.
Is there a public repo somewhere? I don't see any obvious repo for it in
Room supports final fields (yay!), which probably will suffice for many people with respect to this feature request.
an...@backx.org
Room supports immutability (it can use arg constructors) but does not directly support AutoValue. It is in the schedule but not high priority :/. Idk much about its internals at this stage so I'm not sure how we would implement it but should be totally doable.
Sorry we don't have the source release yet :/.
Sorry we don't have the source release yet :/.
il...@google.com
"It is in the schedule but not high priority" -- completely understandable.
"Sorry we don't have the source release yet :/." -- ah, OK, I thought perhaps with the pull request comment, that meant that there was a repo somewhere that I had overlooked.
Thanks!
"Sorry we don't have the source release yet :/." -- ah, OK, I thought perhaps with the pull request comment, that meant that there was a repo somewhere that I had overlooked.
Thanks!
an...@backx.org
Add autovalue support also means you can easily achieve parcelable by https://github.com/rharter/auto-value-parcel . Please consider support this.
be...@google.com
AutoValue is really a handy way to ensure data integrity.
il...@google.com
Please add AutoValue support. AutoValue is a Google library with really good benefits such as toString() , hashCode() , AutoValue.Builder , checks at creation time if @NonNull values are null, etc.
il...@google.com
FWIW,
an...@backx.org
@Yigit: That appears to be a private ticket. Any way we can have access to keep up with it?
il...@google.com
Have any updates?
ra...@gmail.com
news?
Description
Version used: 1.0.0-alpha02
Devices/Android versions reproduced on: Nexus 5, OnePlus One
We want to implement nested NavHostFragments because we want to navigate between 2 screens that each have 2 different Bottom Navigation Bars. We also thought about nesting NavHostFragments so we can bind ViewModels to a navigation part of our app. Parts that need to clean up the data they were using after being navigated through. The problem we're facing is that the outer most NavHostFragment intercepts the back button navigation before the child NavHostFragments do. The result is that when pressing the back button, it completely goes back to the destination before the child NavHostFragment. Are there any plans to support nesting NavHostFragments or is there a different solution to nested navigation that is seemingly not supported by nesting navigation graphs because I don't see how you can for example navigate between fragments with different Bottom Navigation Bars and navigate the fragments that belong to the Bottom Navigation Bar?