setMaxLifecycle() should support Lifecycle.State.INITIALIZING [159662173]

Fixed

Feature Request

Status Update

No update yet.

Description

il...@google.com

created issue #1

Jun 23, 2020 12:25AM

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().

Comments

ap...@google.com <ap...@google.com> #2Aug 14, 2020 01:10AM

Hi Ed, Thank you so much for these suggestions. I've been reviewing them and merging them in. Hopefully it should be live. I've included a thank you note too in the article.

jb...@google.com <jb...@google.com> #3Aug 25, 2020 07:19PM

Marked as fixed.

Great! Thanks a lot, I'll look for the live updates soon!

Issue 159662173

Description

Issue summary

Comments

ap...@google.com <ap...@google.com> #2Aug 14, 2020 01:10AM

jb...@google.com <jb...@google.com> #3Aug 25, 2020 07:19PM

Add comment

Issue metadata