slack-ruby-client
slack-ruby-client copied to clipboard
A Ruby and command-line client for the Slack Web, Real Time Messaging and Event APIs.
We generate endpoints, should also generate tests that have bare minimum expectations around these. See https://github.com/dblock/slack-ruby-client/pull/8.
See groups, ims and channels.myHistory in https://github.com/cixtor/slackapi/blob/master/README.md, ported out of #45.
Like #16 & #26 But just using a `Thread`. There is just one socket opened, so there can be just one Thread with the client running in the backround.
Make properties of web and RTM client, such as users, team or channels, first class models with well-known properties. Right now they are just hashes.
Along with #5 bringing `Celluloid`, allow use of the [http](https://github.com/httprb/http) gem which supports `Celluloid::IO` ... It allows evented `HTTP` and would allow instances of the Slack client to be pooled,...
Update API from [slack-api-ref](https://github.com/slack-ruby/slack-api-ref). Rev: 8a22e57 Date: 2024-06-30
Quite possibly, I'm doing something wrong, but after countless tries, I can't pinpoint where the real time example falls short. To reproduce, create the app and bot OAuth token: *...
randomly client.on :message stops listening to RTM No logs even stored after that on the supplied logger but the app shows as connected. No clue what exactly happens, same code...
fixes: https://github.com/slack-ruby/slack-ruby-client/issues/482 Currently when we get the error message we get no details of what went wrong unless we get the response_metadata for the error which is not intuitive as...
I see we have cassettes here https://github.com/slack-ruby/slack-ruby-client/blob/bf5bb4be3e03e9bd74d22942a61d5611f5c1d997/spec/fixtures/slack/web/views_open_error.yml#L79 but the error we get, if something fails, is just `invalid_arguments`, is this on purpose?