-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update notifications to use @{user_id} #1
Comments
Not sure how to implement. Is there an example of how to perform this lookup? I can see using "event" rather than "body" as in this commit: Not sure what can parse @(user_id} into user. I can see its use in an example that passes a string through ack() but we want to send this to logger. doorbot_1.3/experiments/slack_test3.py Line 19 in 0f6dede
|
The primary issue here is that slack has deprecated usernames for some time. (Before our users started using the app). Instead of being prompted to set a username directly during onboarding it's now taken from the username specified in their email address. In most cases this works fine, but unfortunately so many of our members use dedicated addresses for each service it looks like we have a bunch of
For text that's sent back into Slack (which is what this issue is referencing - For feeding it into a logger I'd use something simliar to the name mapping used in Note: The page on slack user objects kinda implies that all those fields (the display_name/real_name fields in particular) are there for all user objects. The |
🤣 surprisingly unsurprised, and a little proud! No other service I've come across has had this issue, and mostly I just get blank stares and requests for confirmation when I tell them my email address really is [email protected]. |
No description provided.
The text was updated successfully, but these errors were encountered: