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

Merge Develop into Master post Meeetup talk #29

Merged
merged 54 commits into from
Jan 9, 2018
Merged

Merge Develop into Master post Meeetup talk #29

merged 54 commits into from
Jan 9, 2018

Conversation

kylesykes
Copy link
Collaborator

Time to get these changes into the production version at work, and to get all the work Jay did in there.

JacobJerrell and others added 30 commits November 13, 2017 12:45
Adding functions/methods to prevent the bot from sending PM's. Currently working for InMemoryStorage
Added PM Preferences methods to AzureStorage(storage) class
Added methods to RedisStorage to make use of the PM Preference setting. (left commented out)
switched to dev branch, back to InMemoryStorage only
Removed debugging lines, got rid of/commented out unused code
Remove spaces. PM Preference options are now in Azure, Redis, and InMemoryStorage.
Testing is needed for Azure, and Redis
if/elif/else clause to handle user's pm preference options when the bot needs to send a message
Something goofy happened previously. PM Preference options are coded out for Azure and Redis storage options now.
Testing still needed.
ignore it
Checking for length of self.parts to decide if it should act as a toggle. Instead of a try/except for an IndexError
Testing the possibility of having the bot reply to user's request for a leaderboard/fullboard.
Bots do not appear to be capable of posting code snippets. So this is an alternative way of 'collapsing' the leaderboard
Allow the bot to reply to a user's request for a leaderboard/fullboard since bots are not capable of posting/attaching code snippets
fixed it!
Ability to silence DM messages from HeyFireball #14
Updated InMemory storage with Total and Daily ability.
Matt Pitlyk and others added 23 commits November 18, 2017 22:23
Fixed bug around target_id_only not getting set.
There was the potential for an inconsistency in the event that a user passed any argument other than on/off.

It would cause things like having the bot pm the user the setpm off message because PM's were actually on for the user.

This patch prevents that issue by giving a third possible return value of 2. If '2' is returned, the bot will make no changes, inform the user that it can't understand the argument, and show the user the arguments that are accepted for the setpm command.

The _extract_setting method has also been updated to stop hardcoding indexes, matching the above _extract_** methods
@JacobJerrell
Copy link

Please review Pull Request #28 before merging develop into master. There is some wonky behavior that can arise with the setpm command in its current state

Simplification & bug-fix of _extract_setting
@kylesykes kylesykes temporarily deployed to heyflame December 18, 2017 14:03 Inactive
@kylesykes kylesykes merged commit 731aa20 into master Jan 9, 2018
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 this pull request may close these issues.

3 participants