Philip Wedemann

Did you add the import for `error`? Otherwise, the std lib error function is used, which crashes your application as expected. ```kotlin import androidx.compose.material.TextField import androidx.compose.runtime.remember import androidx.compose.runtime.mutableStateOf import androidx.compose.ui.Modifier...

@eymar What about the test of the PR? :D https://github.com/JetBrains/compose-jb/pull/2308/files#diff-96fe1b0a96b139b5b9b4fd22973cc6e48a52b8eb3fd477296bc29cb40b7b85b8

I did try to make `style` composable too, but the non composable test `attrsBuilderCopyFromPreservesExistingAttrs` failed (or my setup is somehow broken...)

@eymar Thanks for the feedback! The goal is to support `display-grid` (and some other css features): https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Grid_Layout In the sample of MDN, they use classes and bootstrap-compose generates these class...

I don't know, I didn't start the rewriting yet. Because I want to use the inline style api instead, I don't need a generated id (no `` elements) in the...

@erikhuizinga Yeah, that's true and I think, we should not to enable `@Composable` in attrs scope because the usage is unambiguous, like you said. The option `composableCalculation` would be more...

Thanks for looking into it. Maybe this is the cause for the unsupported `@Composable AttrsScope`? :D I am okay with keeping the current behavior.

https://github.com/JetBrains/compose-jb/tree/master/examples/web-with-react

I do know how to use the plugin. I would just publish the plugin on mavenCentral as fallback too instead relying only on the gradle portal servers.

Ktor 2.1.0 uses 1.3.3 and you use Kotlin Native (iOS) which could cause the error because of some binary incompatibilities. ``` io.ktor:ktor-serialization-kotlinx:2.1.0 | | | +--- org.jetbrains.kotlinx:kotlinx-coroutines-core:1.6.4 (*) | |...