Zach Klippenstein comments

Results 114 comments of


                                            Zach Klippenstein

Thoughts on decoupling render pass from view updates, and better support support for immediate state change / output

Could you give a more specific example of a workflow that emits output as a function of state @0legg?

Resolve running(Worker) inconsistencies

We decided to remove this from 1.0 in kotlin since it just added work and confusion and we didn't think this was a very important detail to converge on.

Demonstrate driving time machine from a progress bar / slider on a notification.

I think we might be able to just use `MediaSession` for this even though we're not actually playing any media… need to look at the API more.

Replace receiveOrNull with receiveOrClosed once released.

Tried using the preview version of `receiveOrClosed`, but turns out it's broken (https://github.com/Kotlin/kotlinx.coroutines/issues/1584) and caused a set of bugs with odd stacktraces (#626).

Replace receiveOrNull with receiveOrClosed once released.

The referenced coroutines bug was fixed some time ago. Might want to give this another try.

[both] Document and provide more samples for nesting containers

Since this is just a TODO for more samples, I'm removing from 1.0.0.

Compose's insets are lost through a backstack container

I wonder if this has something to do with view/compose interop?

Resolve render(workflow) inconsistencies

We decided to remove this from 1.0 in kotlin since it just added work and confusion and we didn't think this was a very important detail to converge on.

Add Gradle logic to validate RequiresOptIn annotation dependencies and automatically opt-in our own code

Filed issues to Kotlin for these: - annotation classpath requirement: https://youtrack.jetbrains.com/issue/KT-46064 - `api` dependency requirement: https://youtrack.jetbrains.com/issue/KT-46065

Proposal: Introduce `WorkflowUICommon`

I believe this is the approach we're currently using in kotlin.