IssueTracker

Component used: Fragment Version used: 1.3.0-alpha08

Currently the only way to destroy a fragment but to retain it's ViewModel is to put it in the detached state. With the move to a single lifecycle, this will no longer work. Some use cases:

• Custom backstack implementations (allows a migration path for existing ones that are using attach/detach today).
• Recreating a fragment on configuration change. As an optimization you may be telling your activity that you are handling config changes yourself (ex: you have a video player on screen). However views/layouts often don't work well with this approach so it'd be easier to tell certain fragments to recreate themselves.