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
We currently don't have a proper workflow for our Discord slash commands bot. So I need to make a proper symmetric diagram of each and every slash command to audit how each command works.
Expected Behavior
We will have a proper workflow document to check when and why a function inside a slash command is called.
We can check all the logic behind a single command & judge if it's a proper way to do it or not.
This document can be used to understand the workings of our discord slash command in a better way and quickly.
Current Behavior
We currently don't have any workflow documents for our Discord slash command bot.
As we don't have any symmetric diagram of each and every slash command, it makes newbies lives a bit harder.
Currently, it's not easy to understand the whole OPEN-SOURCE repo for beginners and contribute to it.
Screenshots
Reproducibility
This issue is reproducible
This issue is not reproducible
Steps to Reproduce
Severity/Priority
Critical
High
Medium
Low
Additional Information
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:
SkidGod4444
changed the title
Create a symmetric diagram of each and every slash command.
Create a sequence diagram for all discord slash commands.
Nov 7, 2024
Issue Description
We currently don't have a proper workflow for our Discord slash commands bot. So I need to make a proper symmetric diagram of each and every slash command to audit how each command works.
Expected Behavior
Current Behavior
Screenshots
Reproducibility
Steps to Reproduce
Severity/Priority
Additional Information
Checklist
The text was updated successfully, but these errors were encountered: