aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Remove auto_link_display parameter from unfurl_refsTrygve Aaberge2020-02-202-7/+5
| | | | | This is only used in tests, and there we can override the config instead.
* Support blocks of type imageTrygve Aaberge2020-02-191-0/+6
|
* Improve unfurling of text objects in blocksTrygve Aaberge2020-02-191-13/+11
|
* Don't crash when getting block action types other than buttonTrygve Aaberge2020-02-191-1/+8
|
* Tweak formatting of blocksTrygve Aaberge2020-02-191-6/+6
|
* Merge pull request #729 from aereaux/masterTrygve Aaberge2020-02-191-0/+39
|\ | | | | Add implementation of slack layout blocks
| * manage unsupported block and rich textGianluca Arbezzano2020-02-181-1/+3
| | | | | | | | | | | | | | | | | | I added support for reach_text block otherwise at the end of all messages wee-slack was printing the raw JSON block. I have also fixed the `call` block to print the right join url Signed-off-by: Gianluca Arbezzano <gianarb92@gmail.com>
| * Use color_deleted for unsupported blocks.Aidan Epstein2020-02-181-1/+1
| |
| * Fix unfurl_blocks call placement and add a message about unsupported blocks ↵Aidan Epstein2020-02-181-4/+5
| | | | | | | | inside the message.
| * Log errors to a proper debug location.Aidan Epstein2020-02-181-2/+2
| |
| * Add support for the call blockGianluca Arbezzano2020-02-181-0/+2
| | | | | | | | | | | | This commit adds the support for call block. It fixes #726 Signed-off-by: Gianluca Arbezzano <gianarb92@gmail.com>
| * Fix message formatting by calling render_formatting.Aidan Epstein2020-02-181-3/+7
| |
| * Handle a couple more cases. Also add some debug output.Aidan Epstein2020-02-181-8/+21
| |
| * Add initial implementation of slack blocks display.Aidan Epstein2020-02-181-0/+17
|/
* Add options for hard coded colorsTrygve Aaberge2020-02-012-3/+23
| | | | Fixes #681
* Support sending reactions with emoji charactersTrygve Aaberge2020-02-011-7/+23
| | | | Fixes #236, fixes #575
* Render emojis as emoji charactersTrygve Aaberge2020-02-015-1642/+11570
| | | | Fixes #465
* Print error message when reaction couldn't be added/removedTrygve Aaberge2020-01-231-1/+17
|
* Set members correctly in handle_conversationsmembersTrygve Aaberge2020-01-231-3/+2
| | | | | Because this sat channel.members directly instead of calling set_members, the nicklist wasn't updated.
* Set channel.is_member when channel is createdTrygve Aaberge2020-01-221-0/+1
| | | | | | | | | The channel dict sent as kwargs to SlackChannel from handle_rtmstart contains the is_member property. However the one from process_channel_created doesn't. Since you never are a member when the channel is created, we can set it to false (if you create the channel yourself or is invited immediately a channel_joined message will follow the channel_created message).
* Support using a different color for each thread suffix/prefixTrygve Aaberge2020-01-222-9/+21
| | | | Fixes #716
* Fetch members explicitly for SlackPrivateChannelTrygve Aaberge2020-01-221-0/+7
| | | | | | | | | | | Like SlackSharedChannel, SlackPrivateChannel doesn't include members in the result from rtm.start, and we have to use conversations.info for them which doesn't include members either. Therefore, we have to call conconversations.members. I hadn't noticed that the members were missing because I only tested with channels with a short backlog, so the members were filled by the join messages which were still present in the history that were fetched.
* Use GitHub Pages for the OAuth redirect pageTrygve Aaberge2020-01-222-9/+78
| | | | | | This adds a page which shows the OAuth code, and sets the redirect_uri for the OAuth link to this page. This url includes # at the end so the OAuth code is only seen by the browser, and not sent to the server.
* Replace pip with pip3 in readmeTrygve Aaberge2020-01-211-1/+1
|
* Release v2.4.0v2.4.0Trygve Aaberge2020-01-165-3/+58
|
* Use Python3 websocket-client (#731)Jay Williams2020-01-091-1/+1
| | | When installing on OpenBSD, you need to specify the Python 3 version (not Python 2)
* Add a command to list the Slack teamsTrygve Aaberge2019-10-161-0/+13
| | | | | This can be used when you want to remove a team, so you know which token to remove.
* Use max of submessages and replies for number_of_repliesTrygve Aaberge2019-10-032-1/+38
| | | | | | | | | When new replies come in over websocket, we don't update the message_json of the parent message with the new replies, we just append the new message to the submessages list. Therefore, the number_of_replies function has to check both of these and take the max. Fixes #722
* Update dependency instructions for python 3Trygve Aaberge2019-10-011-2/+2
|
* Update README.md (#719)oksiquatzel2019-10-011-0/+1
| | | | | | It tooked me a while to figure out why weechat says that websocket module was not found in wee-slack plugin. pip list sayed websocket-client was installed. after installing pip3 and websocket-client with pip3, everything worked fine. The current ubuntu 19.04 `python-websocket` package has always installed the python2.7 version.
* Add basic support for private channels converted from publicTrygve Aaberge2019-10-013-11/+111
| | | | | | | | | | | | | | | | | | This is for channels which initially were public, but then are changed to private. They look the same as groups (channels initially created as private) in the official clients, but can only be used with the conversations api. They are listed in the channels list of rtm.start with is_private set to true. There are some remaining issues, which are documented in the readme. I'm not sure if we can support read sync and showing unread on load without changes from Slack to the API. Showing thread messages in the channel is possible to fix, but we would have to send requests to load the thread history for all the messages in the history that has replies. Fixes most of #644
* Print thread broadcast messages in parent channelTrygve Aaberge2019-10-011-3/+8
| | | | Fixes #620
* Add documentation for how to send multiple linesTrygve Aaberge2019-10-011-0/+40
|
* Print user friendly error in handle_conversationsmembersTrygve Aaberge2019-08-261-2/+7
| | | | Fixes parts of #714
* Fix process_subteam_created after adding is_member to SlackSubteamTrygve Aaberge2019-08-251-2/+3
| | | | | | | | This was broken in commit 6f9339b. I haven't verified that is_member is set to the correct value when a user group is created, because I don't have access to a slack team where I can create user groups right know.
* Show if user is external in /slack usersTrygve Aaberge2019-08-251-2/+9
|
* Don't list dms and mpdms in /slack channelsTrygve Aaberge2019-08-251-1/+2
|
* Add the usergroups you are a member of to highlight wordsTrygve Aaberge2019-08-251-11/+23
| | | | | | Also shows if you are a member or not in the command /slack usergrous. Fixes #272, fixes #367, fixes #542
* Add nicks without @ prefix to nick completionTrygve Aaberge2019-08-251-0/+1
| | | | | This allows you to complete nicks without a leading @ in buffers we don't show the nicklist, i.e. the team buffer and thread buffers.
* Complete all nicks on the team for some commandsTrygve Aaberge2019-08-251-1/+7
|
* Add support for the /invite commandTrygve Aaberge2019-08-251-0/+48
| | | | Fixes #698
* Linkify users in /slack slash commandTrygve Aaberge2019-08-251-3/+4
| | | | | | | | If we don't linkify users, only usernames (which are not shown anymore) are accepted by the chat.command endpoint, not display names. It does accept user links, so we can use that. However, it doesn't seem to accept channel links (at least the invite command, which is what I tested), so we only linkify users.
* Print responses and errors from /slack slash commandTrygve Aaberge2019-08-251-1/+16
| | | | Fixes #369, fixes #374
* Replace weechat with w a few placesTrygve Aaberge2019-08-251-7/+7
| | | | We should always use w, so we go through the WeechatWrapper.
* Remove url from rtm start test dataTrygve Aaberge2019-08-251-1/+1
| | | | So it doesn't try to connect to the websocket when running the tests.
* Match all channel and user prefixes in unfurl_refsTrygve Aaberge2019-08-251-4/+4
| | | | | | I don't know all the possible prefixes, and I don't think it's a problem to just match # and @. The prefixes I've seen for channels are #C, #D and #G, and for users @U and @W.
* Refactor linkify_text to use re.subTrygve Aaberge2019-08-252-27/+25
| | | | | Instead of splitting the message at spaces and checking and replacing each word, use re.sub for the whole message.
* Support @everyone in linkify_textTrygve Aaberge2019-08-252-1/+6
|
* Add some more tests for linkify_textTrygve Aaberge2019-08-252-0/+39
|
* Refactor unfurl_refs to use re.subTrygve Aaberge2019-08-251-36/+31
| | | | | Instead of finding each match and calling replace on the text with that match, use re.sub to replace all the matches.
generated by cgit (git 2.34.1) at 2024-11-18 12:36:06 +0000