respond() doesn't take a function as its data argument

[steph643]

In the source code, respond() is advertised as being able to take a function as its data argument:

/**
   *  A convience method for listening to an event and then responding with some data
   *  right away. Automatically removes the listener
   ...
   *  @param {Object} [data = {}] The object to pass back.
   *  	May also be a function; the return value will be sent as data in this case.
   ...
   */
respond(event, data = {}, runOnce = false) 

But it doesn't work. Only plain objects are supported.

This is too bad, as doing some dynamic computation before sending the data back is often required.

[steph643]

Workaround: return a plain object with one field initialized with a function call.

bellhop.respond('init', {
  myData: (() => {
    // Computation here
    ...
    return result
  })()
})

[chipbell4]

You're absolutely right. This probably should be a feature, and it looks like we intended to but forgot. We'll get that knocked out shortly and release a 2.4.0

[chipbell4]

This should be resolved now!

• It's tagged here on github
• It's also published to npm