Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hubot scripts have no access to Campfire message IDs #401

Closed
aroben opened this issue Jan 22, 2013 · 3 comments · Fixed by #402
Closed

Hubot scripts have no access to Campfire message IDs #401

aroben opened this issue Jan 22, 2013 · 3 comments · Fixed by #402

Comments

@aroben
Copy link
Contributor

aroben commented Jan 22, 2013

There seems to be no way to get access to a Campfire message's ID from within a Hubot script. It looks like the Campfire adapter receives these IDs but then doesn't pass them on to the TextMessage/EnterMesage/LeaveMessage objects.

It would be handy to have access to these message IDs so you can, e.g., generate links to Campfire transcripts from within a Hubot script.

/cc @jonmagic

@tombell
Copy link
Contributor

tombell commented Jan 22, 2013

@aroben give that branch a glance, the ID should be available in msg.message.id, I've tested it locally with Campfire, and as long as the value I think is the message ID is the message ID, should be good for what you need.

@aroben
Copy link
Contributor Author

aroben commented Jan 22, 2013

@tombell Wow, awesome! That branch looks perfect. 💖

@jonmagic
Copy link
Contributor

🤘

On Tuesday, January 22, 2013 at 9:18 AM, Tom Bell wrote:

@aroben (https://github.com/aroben) give that branch a glance, the ID should be available in msg.message.id, I've tested it locally with Campfire, and as long as the value I think is the message ID is the message ID, should be good for what you need.


Reply to this email directly or view it on GitHub (#401 (comment)).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants