Create a Lint warning to replace <fragment> with FragmentContainerView [139830056]

Fixed

Feature Request

Status Update

No update yet.

Description

il...@google.com

created issue #1

Aug 21, 2019 11:14PM

Component used: Fragment
Version used: 1.2.0-alpha02

Once FragmentContainerView supports android:name (from

https://issuetracker.google.com/issues/139830628), it would be nice to have a Lint warning that would ask developers to replace the old <fragment> tag with <androidx.fragment.app.FragmentContainerView> in order to get the unified lifecycle.

Comments

jb...@google.com <jb...@google.com> Oct 2, 2019 03:48AM

Reassigned to fr...@google.com.

ap...@google.com <ap...@google.com> #2Oct 3, 2019 04:34PM

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.

il...@google.com <il...@google.com> #3Oct 7, 2019 07:27PM

Marked as fixed.

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

b9...@gmail.com <b9...@gmail.com> #4Oct 9, 2019 08:20PM

Sorry, what should I do when inflate NavHostFragment via xml? In the document it use <fragment> tag to inflate NavHostFragment.

https://developer.android.com/guide/navigation/navigation-getting-started#add-navhostfragment

il...@google.com <il...@google.com> #5Oct 9, 2019 08:22PM

Replace <fragment> with FragmentContainerView. As per this tweet (

https://twitter.com/ianhlake/status/1182006577261268993), we'll be updating documentation across

d.android.com after this release goes stable.

11...@gmail.com <11...@gmail.com> #6Oct 9, 2019 09:37PM

I've tried this fix and failed; Got it working after replacing `android:name="androidx.navigation.fragment.NavHostFragment"` with my start destination fragments' name.

Is this the intended way of using `FragmentContainerView` with navigation? Or am I confused(as per usu...)?

Thanks,
Jon.

11...@gmail.com <11...@gmail.com> #7Oct 9, 2019 10:08PM

Scratch my comment.

Changing the name attr only "works" for a single fragment activity. Sorry.

I ended up reverting back to <fragment/> for now.

il...@google.com <il...@google.com> #8Oct 9, 2019 10:58PM

We're tracking a bug with FragmentContainerView with parsing attributes not working, something that NavHostFragment in particular requires.

Feel free to star

https://issuetracker.google.com/issues/142421837 to track progress on the fix (and for now just continue to use <fragment> for those cases).

bi...@mail.de <bi...@mail.de> #9Oct 24, 2020 02:56PM

Please only suggest the lint fix if the <fragment> is inside a FrameLayout and/xor is the only child of the parent layout.

In my case I want to inflate a Fragment provided by some lib in my in some nested LinearLayout and the replacement doesn't make sense at all in this case.

il...@google.com <il...@google.com> #10Oct 25, 2020 10:40PM

Re #9 - You should always, always inflate a fragment into a FragmentContainerView. There is no exception where you should continue to use <fragment>. You can, of course, put your FragmentContainerView in any layout you want, LinearLayout or otherwise.