Manually call a .respond listener

I’m wondering if there’s a best practice way of manually calling a .respond listener. In some instances, it would be great if I could manually call one and let params go through as default (eg, msg.match[1] for example will match nothing and fallback to default).

Normally, the action performed by the listener being called would be abstracted out but I’m just curious if anyone else has gone this way.

For example

module.exports = (robot) ->
  robot.respond /hello!/i, (msg) ->
      msg.send "Hello to you too, sir!"
      # Something here to call the below listener and have Hubot also wish the user a great day

  robot.respond /have a great day/i, (msg) ->
      msg.send "I wish upon you a fantastic day, as well!"

[xrysanthos]

Hi all! This type of functionality is really important when it comes down to re-using behind the scenes 3rd party script packs. For example if I’m building a script pack for my specific business context it would be great if I could just execute one or more commands exposed by another library (e.g. google maps scripts, etc) explicitly by using its text patterns.

This way developers can really work on the semantic layer of things without having to worry about internal listener IDs and other low-level stuff. @michaelansel solution is clean but cannot work with existing libraries if no IDs have been specified for each listener.

For example if my listener hears for:

get service x location

and I’m using hubot_maps as a dependency, my service would return the location details in the controller and if I wanted to enrich the message with geo info I’d just have an extra step calling

hubot map me ‘query’

passing the coordinates, get its response and return the enriched message.

Command composition is definitely a great way of leveraging re-usability.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.