Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
Can you rise priority please?
It's a real stopper to use in not helloworld apps.
It must be joke, define it as "An issue that should be addressed eventually. Such an issue is not relevant to core organizational functions or the work of other teams, or else it relates only to the attractiveness or pleasantness of the system."
Why use compose in production, if this base things resolved for years?
It's a real stopper to use in not helloworld apps.
It must be joke, define it as "An issue that should be addressed eventually. Such an issue is not relevant to core organizational functions or the work of other teams, or else it relates only to the attractiveness or pleasantness of the system."
Why use compose in production, if this base things resolved for years?
jb...@google.com <jb...@google.com> #3
This is high priority for us. The "Priority" field on buganizer is misleading, it has a very specific internal meaning and interaction with other systems so we don't use it for actual prioritization for compose text issues. Unfortunately, the way we track actual priority is not visible externally.
Description
When adding the defaultCreationExtras for NavBackStackEntries in https://issuetracker.google.com/207012490 , we should have also made the default
ViewModelFactory
stateless so that when using the default factory, we actually created view models via the extras.We need to make the factory stateless to complete the feature integration.