slack-ruby / slack-ruby/slack-ruby-client
support posting to response_url for message actions (buttons)
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 1.3k
- Forks
- 222
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 3
Description
When creating messages with interactive buttons, one of the ways to update the message after someone hits a button is to use make a request to the response_url, which is included in the action payload. It would be very convenient if this client could make those requests.
I did some initial poking around: I tried using the response_url as the endpoint, and then put the updated message content in the body, but I got Faraday::ClientError: the server responded with status 500, so I think I don't understand Faraday.
https://api.slack.com/docs/message-buttons#how_to_respond_to_message_button_actions
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Slack message-buttons documentation linked in the issue and inspect the client’s existing Faraday request handling; no file or test is named. Done means the client can post updated message content to the action payload’s response_url without the reported 500 error, with coverage for the new request behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100