WorkflowRuntime re-write with Compose tree mechanisms?

[steve-the-edwards]

trafficstars

Placeholder for this thought in the optimization backlog.

@zach-klippenstein and I once talked about re-writing the WorkflowNode tree using compose mechanisms (and optimizations?) but the problem there (IIRC) was that we don't want to have multiple compose-node types in the same app (e.g. UI compose-nodes and then Workflow nodes).

[rjrjr]

I think that's supported now.

On Tue, Feb 15, 2022, 3:01 PM Stephen Edwards @.***> wrote:

Placeholder for this thought in the optimization backlog.

@zach-klippenstein https://github.com/zach-klippenstein and I once talked about re-writing the WorkflowNode tree using compose mechanisms (and optimizations?) but the problem there (IIRC) was that we don't want to have multiple compose-node types in the same app (e.g. UI compose-nodes and then Workflow nodes).

— Reply to this email directly, view it on GitHub https://github.com/square/workflow-kotlin/issues/665, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOMCHJ6PRI4OT5WCCSQ4HLU3LLLJANCNFSM5OP553QA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[steve-the-edwards]

The work is being done in #824 some discussion in https://github.com/square/workflow-kotlin/discussions/272

[steve-the-edwards]

See discussion here for future ref: https://www.reddit.com/r/androiddev/comments/1an5emm/comment/kqf8dz0/