-
Notifications
You must be signed in to change notification settings - Fork 638
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
Special treatment for names and channels (@ and #) #9
Comments
I don't think the issue here is the URL parsing. Names are mangled into internal ID's before the request is sent. Any chance we could have those as plain text? |
I will unmangle in the internal code that sends to hubots. |
Thanks @grantmd |
Wooo! 👍 |
Released. Hopefully made 100% better and 0% worse. |
@grantmd confirmed that usernames look delightfully unmangled for us |
Wahoo! I shall share with the team! |
@grantmd thank you! |
Ok, still having issues, should we re-open this issue to change how hubot-slack processes the @NAMEs? |
Yeah, the @ is intentional, but I can remove it from hubot messages if you like. |
Cool. If you have time, but I can also convert this to a PR later when I get some time |
Currently, using a designation that would be hyperlinked (#channel and @username) will send a nonsensical internal id to the bot. If this is simply a matter of providing special case where, if the hyperlinked text starts with
@
or#
, then use the link text and not the link url:https://github.com/tinyspeck/hubot-slack/blob/master/src/slack.coffee#L78-L79
The text was updated successfully, but these errors were encountered: