IssueTracker

Component used: fragment-compose

Version used: 1.7.0-alpha09

My app extensively uses the Fragments with ComposeViews in them. I was trying out new content extension from fragment-compose, but I noticed a lot of my ComposeViews interact with window insets but do not consume them. Therefore, the initialization code for these views looks like this:

override fun onCreateView(...): View {
    return ComposeView(requireContext()).apply {
        setViewCompositionStrategy(DisposeOnViewTreeLifecycleDestroyed)
        consumeWindowInsets = false
        setContent {
            AppTheme {
                ... // a lot of code
            }
        }
    }
}

After migration to the content extension, because ComposeView is not available until after content returns, consumeWindowInsets must be placed after the content lambda:

override fun onCreateView(...): View = content {
    AppTheme {
        ... // a lot of code
    }
}.apply { consumeWindowInsets = false }

It would look much better if consumeWindowInsets was a parameter of the content function:

override fun onCreateView(...): View = content(consumeWindowInsets = false) {
    AppTheme {
        ... // a lot of code
    }
}

Sure, it's easy to declare such a content function in project, but I think it might be worth considering putting it into fragment-compose.