-
Notifications
You must be signed in to change notification settings - Fork 160
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
Plugins updated + Heroku config #1
Conversation
Love the Heroku config, but I don't get why you need to pass the message text, instead of the request form, into the plugins. My problem with that is that it prevents the plugin writer from accessing any of the other fields in the request; what if they want to whitelist/blacklist users, for example? |
I was afraid of that. I was trying to make it compatible with the 'daemon' version since I don't my 'body' variable is similar to your 'request.form' variable, but mine is Do you think in any way to make the body and request.form similar so we can On Sun, Jun 8, 2014 at 8:12 PM, Bill Mill [email protected] wrote:
|
It looks to me like we each have a dictionary-like object with a "text" attribute containing the text of the message. Why wouldn't we be OK just passing that in as the |
Yes we should be ok. Let me test that and update the PR. |
PR updated to use the dictionary-like in the plugins instead of request.form.get so it works the same as I will do for the slackbot daemon |
Sweet! Now you actually don't need to change the plugins at all; |
Learning something everyday :) I will revert that part and update the PR. Sent from my iPhone
|
Ok let only Heroku setup now ;) |
Add Heroku config and doc * Many thanks @fsalum!
Moved out from the msg.get in plugins so they would be compatible with the
daemon version I'm porting it to use with Amazon SQS integration.
Added info to use Heroku to host app for free.
My daemon version is here: https://github.com/fsalum/slackbot-python