You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Few steps are missing when we set up discord-slash-commands along with own bot on our local machine and able to run slash commands.
Expected Behavior
New developer should be able to setup project(own discord bot) locally and connect with rds backend
Current Behavior
Currently new developer is not sure , what is wrong with token formatting while connecting with rds backend and how to reflect command changes in discord bot server. Also, there is a confusion from where one can get .workers.dev url.
Screenshots
No snippet.
Reproducibility
This issue is reproducible
This issue is not reproducible
Steps to Reproduce
Setup discord-slash-command with own bot and connect with rds backend
Severity/Priority
Critical
High
Medium
Low
Checklist
I have read and followed the project's code of conduct.
I have searched for similar issues before creating this one.
I have provided all the necessary information to understand and reproduce the issue.
I am willing to contribute to the resolution of this issue.
The text was updated successfully, but these errors were encountered:
Issue Description
Few steps are missing when we set up discord-slash-commands along with own bot on our local machine and able to run slash commands.
Expected Behavior
New developer should be able to setup project(own discord bot) locally and connect with rds backend
Current Behavior
Currently new developer is not sure , what is wrong with token formatting while connecting with rds backend and how to reflect command changes in discord bot server. Also, there is a confusion from where one can get .workers.dev url.
Screenshots
No snippet.
Reproducibility
Steps to Reproduce
Severity/Priority
Checklist
The text was updated successfully, but these errors were encountered: