Wrap actions from unbatched lists in the tagger from Cmd.map

[bdwain]

@laszlopandy this should address the list issue from #218

[bdwain]

the key is here. We use the wrapped dispatch rather than the vanilla one.

I could see something like this maybe being needed in the new timeout/delay Cmd types also, but we can deal with that after this is merged (or I will add it if that gets merged first)

[laszlopandy]

Yes, I also realized this will be an issue for Cmd.setTimeout. And yes we can solve it separately.

[laszlopandy]

@bdwain I had another idea after reading the discussion of the return type of dispatch #237

What if instead of returning Promise<Array<Action>>, executeCmd returned Array<Promise<Action>>? In that way you could maintain the behaviour of parallel list execution (without batch) by returning a list of promises which resolve at different times. The passed dispatch argument would be used solely for run commands that request it with Cmd.dispatch.

The disadvantage is that this idea would require a bigger refactor. On the plus side it makes executeCmd conceptually simpler in that all actions would be returned. Whereas now some are returned (to be dispatched by the caller) and some are dispatched internally.

[bdwain]

@laszlopandy can you make a separate issue to discuss that? It sounds interesting, though I'm not totally clear on what problem it's solving. But I think whatever it is would be separate from this change.

[bdwain]

@laszlopandy one other thing is that that change sounds like it could potentially be a breaking change, and if so, we'll want to wait to do a v6 until we have it merged, since this and a few of the other changes going out are breaking too.