1.0: High-level blockers

[zach-klippenstein]

We are talking more and more about 1.0 blockers informally, and I want to have a central place to track them across both platforms.

• ViewRegistry – should i stay or should i go? (Consider de-emphasizing ViewRegistry. #390)
• mapOutput in Swift vs runningWorker in Kotlin (Swift: change awaitResult(worker …) to running(worker …) #544, Swift: find a better name for mapOutput #583)
• WorkflowAction boilerplate reduction (aka do we bring back emitOutput?) (Proposal: add RenderContext.makeOutputSink #644)
• Data classes break binary backwards compatibility (#779)

[SalvatoreT]

WorkflowAction boilerplate reduction (aka do we bring back emitOutput?)

I mostly use WorkflowAction as a lambda, so it looks like this everywhere.

sink.send(WorkflowAction {
  this.state = EnteringName(state.firstName, state.lastName)
  null
})

[zach-klippenstein]

@SalvatoreT Let's discuss in #644 instead. This issue is for tracking the group of issues, not the actual issues themselves.

[JustinDSN]

Obsolete now that we have discrete tickets and milestones and labels oh my!