Please sign in to comment.
Fix for bug with Hubot sending messages to the wrong room
This fixes an issue where if Hubot joined mulitple rooms, userForId would return the user object with the room attribute from the first message as persisted by Redis. Since the adapter only cares about the room the user belongs to, we can just construct an object that provides that information rather than polluting robot.brain with a fake user object via userForId
- Loading branch information...
Showing with 10 additions and 5 deletions.