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

Investigate say() and respond() #189

Closed
kronosapiens opened this issue Jul 4, 2024 · 1 comment
Closed

Investigate say() and respond() #189

kronosapiens opened this issue Jul 4, 2024 · 1 comment
Labels
maintenance Improving existing functionality maybe A potential update

Comments

@kronosapiens
Copy link
Member

Bolt JS provides some helper functions for responding to requests. If I can use these instead of my own postMessage or postEphemeral functions the codebase can be kept more semantic.

https://slack.dev/bolt-js/concepts

@kronosapiens kronosapiens added the maintenance Improving existing functionality label Jul 4, 2024
@kronosapiens kronosapiens added this to the v0.6.0 milestone Jul 15, 2024
@kronosapiens kronosapiens removed this from the v0.6.0 milestone Nov 23, 2024
@kronosapiens kronosapiens added the maybe A potential update label Feb 11, 2025
@kronosapiens
Copy link
Member Author

In #239 , respond was used to replace the existing replyEphemeral. Looking into say, however, it seems as though there are fewer, if any, opportunities to use it. say is a helper meant to respond to message events -- such as when the app is directly mentioned, or a specific emoji is triggered. These are not flows which we utilize, so we have limited use for say.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Improving existing functionality maybe A potential update
Projects
None yet
Development

No branches or pull requests

1 participant