Skip to content

Instantly share code, notes, and snippets.

@philipwalton
Last active January 3, 2016 03:28
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save philipwalton/8402139 to your computer and use it in GitHub Desktop.
Save philipwalton/8402139 to your computer and use it in GitHub Desktop.
Async events handling strategies
// host library code
program()
.initStuff()
.then(function() {
dispatcher.emit('beforeRenderPost')
})
.then(function() {
dispatcher.emit('afterRenderPost')
})
.then(function() {
dispatcher.emit('beforeWritePost')
})
.then(function() {
dispatcher.emit('afterWritePost')
})
.catch(errorHandler)
// now the user's code can simply be the following and the host logic
// will wait until their async function is finished before continuing
dispatcher.on('beforeRenderPost', doSomethingAsyncToPost)
@philipwalton
Copy link
Author

would basically need to check against the expected Function.length to define if you should wait for callback call or not

I originally considered this. Like, if the callback function's .length property is one greater than the emitter's arguments.length property, assume async, but that won't work 100% of the time. Sometimes a callback will make use of the arguments object for ...rest parameter type situations, so it gets a bit hairy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment