Component used: Fragment Version used: 1.3.0-alpha06

Right now, setMaxLifecycle() only supports Lifecycle.State.CREATED or higher. It would be nice if setMaxLifecycle() could also support Lifecycle.State.INITIALIZING only for Fragments that have never moved above CREATED - i.e., only something that could be set alongside the Fragment being added to the FragmentManager.

This would allow developers and libraries built on top of fragments to keep fragments only at the attached state without going through onCreate().