slack-ruby
Is this repo really legacy, there is still a use case?
Hey @dblock, thanks for all you've done here.
According to Slack (https://api.slack.com/changelog/2021-10-rtm-start-to-stop), the rtm.connect method will still be supported past September 2022?
Indeed if I set that method of connecting as default to a new 'classic' bot, slack-ruby-bot seems to work really well.
The scope of this repo and framework fits my needs better as I don' t need a standalone webserver and a separate db, I can just add it to my existing Rails app (which is intentional as I'm trying to integrate its data with Slack), avoiding a lot of complexity & duplication. So, are we calling time on this repo too early?
Might it make sense to build a back-end-less bot framework on the newer api methods?
Apologies, I'm new to the Slack space and your repos, I'm probably missing some nuances and issues with that approach.
IMO anything on a deprecation path should not be used for anything new. I think something more specific to Rails and that is compatible with https://github.com/slack-ruby/slack-ruby-bot-server-events might make more sense?
What does that optimally look like? What's the most efficient way to get there?
- a cut down https://github.com/slack-ruby/slack-ruby-bot-server? (we need a version without the unnecessary DB and web server?)
- a PR to this repo to remove the legacy parts and migrate to the new API as appropriate?
- a new repo entirely?
- something else?
What does that optimally look like? What's the most efficient way to get there?
I think it's a fork of https://github.com/slack-ruby/slack-ruby-bot-server-events that takes a Rails dependency instead of slack-ruby-bot-server.