Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for custom routes to HTTPReceiver & SocketModeReceiver #866

Closed
4 tasks done
stevengill opened this issue Apr 2, 2021 · 1 comment · Fixed by #1114
Closed
4 tasks done

Add support for custom routes to HTTPReceiver & SocketModeReceiver #866

stevengill opened this issue Apr 2, 2021 · 1 comment · Fixed by #1114
Assignees
Labels
enhancement M-T: A feature request for new functionality
Milestone

Comments

@stevengill
Copy link
Member

Description

Similar to how ExpressReceiver allows defining custom routes, it would be nice if HTTPReceiver and SocketModeReceiver did the same.

This has been requested a few times before. See #834

What type of issue is this? (place an x in one of the [ ])

  • enhancement (feature request)

Requirements (place an x in each of the [ ])

  • I've read and understood the Contributing guidelines and have done my best effort to follow them.
  • I've read and agree to the Code of Conduct.
  • I've searched for any related issues and avoided creating a duplicate issue.
@stevengill stevengill added the enhancement M-T: A feature request for new functionality label Apr 2, 2021
@smoneta
Copy link

smoneta commented May 17, 2021

Im also having issues (lack of knowledge more likely) add ing custom routes in socket mode. I added the code and I'm working on migration the expressReceiver routes I have in order to use them under the SocketModeReceiver. The sample code in the bolt page is great but would be nice to include a sample endpoint too.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement M-T: A feature request for new functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants