The reply_to value overrides the room name. The reply_to seems to encode both the room and the user sending the message so it changes per user. When the enter hook is triggered, it looks up the room name with no reply_to, which would, of course look different. So the flow is:
Receive a message in #devops that matches regexp for telling.
Extract reply_to (C02EKKBLG) and username (parkr)
Save message to localstorage["C02EKKBLG"]["parkr"].
Later, parkr enters #devops. Receive EnterMessage with room devops and username parkr.
Look up localstorate["devops"]["parkr"], but nothing is there.
Not sure whether this is a bug in hubot-slack or in hubot-tell.
I ran into an issue today after #2 was merged. hubot-slack doesn't appear to have the same behaviour as HipChat and therefore fails.
Per my comment in https://github.com/hubot-scripts/hubot-tell/pull/2#issuecomment-165899139:
The
reply_to
value overrides the room name. Thereply_to
seems to encode both the room and the user sending the message so it changes per user. When theenter
hook is triggered, it looks up the room name with no reply_to, which would, of course look different. So the flow is:#devops
that matches regexp for telling.C02EKKBLG
) and username (parkr
)localstorage["C02EKKBLG"]["parkr"]
.#devops
. Receive EnterMessage with roomdevops
and usernameparkr
.localstorate["devops"]["parkr"]
, but nothing is there.Not sure whether this is a bug in hubot-slack or in hubot-tell.