While going through the JetnewsApp, noticed cases ...

# compose

[Tash]

While going through the JetnewsApp, noticed cases of trailing lambdas that were not Composable functions. Seems like we’d eventually need some rules of thumb to follow to reduce ambiguity and improve readability. Perhaps something like:

Use named arguments when
- there is more than one Composable.() -> Unit
- and/or when there are (one or more) () -> Unit s

A small example where this would aid readability:

Before

ModalDrawerLayout(
        ...
        drawerContent = {
            AppDrawer(
                currentScreen = JetnewsStatus.currentScreen,
                closeDrawer = { onDrawerStateChange(DrawerState.Closed) } // But, what is opening the drawer ?
            )
        },
        bodyContent = { AppContent { onDrawerStateChange(DrawerState.Opened) } } // What is AppContent's lambda for?
    )

After

ModalDrawerLayout(
        ...
        drawerContent = {
            AppDrawer(
                currentScreen = JetnewsStatus.currentScreen,
                closeDrawer = { onDrawerStateChange(DrawerState.Closed) } // Close drawer
            )
        },
        bodyContent = { 
            AppContent(openDrawer = { onDrawerStateChange(DrawerState.Opened) }) // Open drawer
        } 
    )