-
Notifications
You must be signed in to change notification settings - Fork 171
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
#379 Set will_is_mentioned even if message was direct #380
base: master
Are you sure you want to change the base?
#379 Set will_is_mentioned even if message was direct #380
Conversation
The old world weather API is no more. The replacement does not provide the local time in the JSON output. The solution is migrating the plugin to use the google apis which provides the timeZoneId, which is definitely enough for the `pytz` to generate a datetime object.
In the console the HTML tags look pretty uggly and it's better to eliminate them completely.
Fix worldtime plugin
…_backend strip HTML tags for shell backend
Feature/dockerized
* Tenzer-all-the-changes: Add Jeppe Toustrup to the AUTHORS list Bugfix: Avoid the use of `locals()` in the reminder plugin Bugfix: Don't report HC/BB state if the previous state wasn't known Pylint: W0612, W0613, remove unused variables Pylint: C1801, don't use `len(i) == 0` as a condition in if statements Pylint: W1201, let the logging functions do string interpolation Bugfix: Correct regex for will.plugins.friendly.mornin plugin Cleanup: Remove broken random_topic plugin Python 3: Run tests in Python 3 along with Python 2 Python 3: Use new way of representing octal numbers Python 3: Fix detection of plugin methods Python 3: Use new form of `except` lines Python 3: Make imports absolute and clean up unused ones Python 3: Use six to handle imports which have changed between 2 and 3 Python 3: Update dependencies on dnspython and natural to get PY3 support Python 3: print is a function, not a statement
…and spelling errors.
Feature/merges in py3
* feature/merges-in-py3: Friendlier location output
… of friendliness.
…cally handled (with explanations)
There was no check whether the given channel name, regular or default, existed. This caused the thread to fail and stall Will until it was restarted.
Fix fabfile with new Fabric v2
Support for slack attachments
Improve slack channel handling
skoczen#348 Scheduled reminders should notify the user who requested them
…ckends Add --backends option to generate_will_project
Improve Slack Connection handling
/cc @unicolet |
let me understand the behavior a little more, if you say
in your WillPlugin, the
? |
@wontonst The respond_to in our case was only set to the |
I see. Let me rephrase my question. With the ability to give the bot a command in the middle of the message, what does the will respond_to look like when you match with anchors? In the example, would will respond to
or
|
PR makes it so
will_is_mentioned
is set, even if message was determined to be direct (Began with the Chatbots handle). Change affects only HipChat and Slack, as RocketChat already seems to have this correct behaviour since it checks the mention list.Simply moved the
will_is_mentioned
to before where the name is stripped out.Fixes #379