Closed davejhilton closed 9 years ago
Very good man, Thanks.
I haven't updated this plugin because I work in another company where we don't use slack (yet). However, if we will start using slack, for sure I'll update this plugin, and make one for PyCharm too.
Any contributions are welcome!
I made a release with your improvements, and it's on live. Should be updated for all users now. Thanks
Hey thanks! I really appreciate you taking the time to do that!
Hey, thanks for this plugin!
I added a few features in a forked branch, mostly to suit my own (and my team's) liking. But then I thought I'd at least submit the changes to you as a pull request in case you think they're worthwhile enough to add to the main package.
disclaimer: my python is a bit rusty—it's been a while...
The biggest change I made was making it so that when the receiver of the message is a specific user (via
@someUser
), it now sends that message as a direct private message using the IM API. Before it would just dump the message into that user's default/slackbot channel, which made it hard to follow up with a conversation about a posted snippet.I also added 2 new optional settings. I've updated the README.md on my forked branch to include explanations of these 2 new settings:
"username_subtext"
"repeat_file_ext"
So that's probably the easiest way to see what they do.
Note that although the
"username_subtext"
setting I added would override the existing"show_platform_and_name"
setting, I tried to "do the right thing" by maintaining backwards compatibility... by making that new setting benull
by default so it's an "opt-in" feature, and by still respecting the original"show_user_and_platform"
setting if it's set totrue
. That way, anyone upgrading shouldn't suddenly have it change behavior on them.Anyway—feel free to reject the merge, and/or change anything I've done before merging. Like I said these changes were mostly to suit my own liking... but I thought it would be great to see them in your package-manager hosted version
Thanks!