now that we have a cohesive look at workflow APIs, some issues remain:
createActivityHandleisnt really a handle, in the way thatcreateWorkflowHandleandcreateChildWorkflowHandleare. it returns a function that you call.- users are confused by the proxy destructure which a very fancy way of doing type safety and ensuring consistent naming
defineSignal/Querydont add much value since they just create an object- extra
setListenerapi that is doing the real work, basically 2 different functions branching bydef.type
- extra
just taking another crack at api design.