Web: Make AttrBuilderContext Composable

https://github.com/JetBrains/compose-jb/blob/471d5c652db20286d478c25c2b3d80ab4200215a/web/core/src/jsMain/kotlin/org/jetbrains/compose/web/elements/Base.kt#L21 It is already Composable, but this feature/annotation is no forward to other calls, namely: https://github.com/JetBrains/compose-jb/blob/471d5c652db20286d478c25c2b3d80ab4200215a/web/core/src/jsMain/kotlin/org/jetbrains/compose/web/elements/Base.kt#L109

Use case: Use remember in the styling api to create ids automatically.

[hfhbd]

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 <style> elements) in the end, if it works. The rewrite should not be composable.

While this snippet/the function sounds helpful, I hope I don’t need it at all 😃 So thanks for the feedback to ask for the real use case.

[hfhbd]

@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 names automatically with a UUID. So we use this:

Style {
    val classname = remember { "_${UUID()}" }

    className(classname) style {
        // apply the styling
    }
}
return classname

and the same class name in the actually HTML element.

But in the end, I dislike this behavior. Instead, I should use the AttrsScope.style function with “in-memory” style sheets than writing the style in the DOM and using the same class name.

While this PR would simplify my current implementation, I think, it would be better to implement it with AttrsScope.style instead, somehow in the long term.

So after rethinking the current bootstrap-compose implementation I would keep the behavior in compose-jb and change my implementation instead.