-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Slash Command Feedback Master List #2490
Comments
What's going on this week? (OK, it was last week) We've been hard at work responding to developer feedback on slash commands. A number of slash command related fixes and small improvements have gone out in the last week, with more significant improvements planned. All of these changes have been completed and merged, but may not yet be deployed on all platforms yet.
|
Hey hey hey! Sorry for the late update. Here is what we've accomplished last week and this week in the world of Slash Commands. Last week was mostly bug fixes because there's some big stuff coming soon 👀
|
Hey hi hello. Back with your not-quite-weekly update about what's been going on! New Features
Improvements
Bug Fixes
|
Thank you all for all the responses and feedback you've given us about Slash Commands during this beta period. GitHub is great for tracking issues, but can sometimes be hard at a glance to understand the status of them without digging through tons of comments and swapping between open/closed.
This issue will serve as a "master list" that shows:
This issue will be locked for comments since it's just a centralized repo.
Bugs We're Squishing
Features We're Adding
Still in Discussion
What We're Not Doing Right Now, and Why
/@me
Command Routes Allow '@me' for /applications/:id/commands endpoint #2332 (comment)GET
global commands of other bots Allow GET /applications/:id/commands for other applications #2337 (comment)default
default field doesn't work in any configuration #2393The text was updated successfully, but these errors were encountered: