Control passed to handler before completing middleware chain about compose HOT 4 CLOSED

You need to return a promise if you do asynchronous activities, which includes calling next IIRC (it's been a while since I've worked with Koa).

Here's a working example: https://gist.github.com/1f0670e88911cac546dc80548bca1865

from compose.

@PlasmaPower your example does work. I'm struggling to understand why though. This feels like Promise black magic haha.

Thoughts on this being an antipattern? My experience with callbacks is that you need to call next before moving on.

from compose.

You're probably thinking of the express model. In Koa, you almost always return a promise.

from compose.

Expanding on @PlasmaPower's answer: Promises need to be chain returned otherwise any of them will resolve and Koa flushes the response. All next calls return a promise guaranteed because of how compose works - meaning that even if you call next expecting it will be a normal function it's actually a promise.

from compose.