A modern programming language that makes developers happier.

kotlinlang

If I'm using my own custom Material theme (MyAppTheme), should I be trying to access something like `isLight` via `MaterialTheme.colors.isLight` or should I basically never be touching MaterialTheme static accessors? (themeing still confuses me, sorry :upside_down_face: )

I would be more concerned about explicitly checking for light mode vs just using the colors that are specified. But if you have a good reason, I don't think there's anything wrong with looking at theme values directly. 

M3 themes no more expose isLight so you might already look for something different to manage this state.

This is what I'm doing

```val systemUiController = rememberSystemUiController()
val useDarkIcons = MaterialTheme.colors.isLight

SideEffect {
  // Update all of the system bar colors to be transparent, and use dark icons if we're in light
  // theme
  systemUiController.setSystemBarsColor(color = Color.Transparent, darkIcons = useDarkIcons)
}```


I did the same but after M3 I know use
```val LocalThemeDarkMode: ProvidableCompositionLocal&lt;Boolean&gt; =
    staticCompositionLocalOf { error("LocalThemeDarkMode not initialized") }```

Could you use `androidx.compose.foundation.isSystemInDarkTheme()` directly as default theme wrapper use it to check which palette to provide?

You can have the system in dark mode and offer an light theme.

Do you want to know if the device is in dark or light theme or if your app user setting is set to light or dark?

I am using the following workaround in material3 because isLight is missing:
```val ColorScheme.isLight get() = background.luminance() &gt; 0.5f```