-
Notifications
You must be signed in to change notification settings - Fork 11
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
Suggestion: Add other interaction types as seperate folders #47
Comments
Could you clarify more? Do you mean something like this?:
|
Yes, exactly. And then in those folders you would be able to place the handlers for those types of interactions. Basically the exact same way the commands and events folders work in commandKit now. Maybe autocomplete doesn't need a seperate folder since it's already handled within command files themselves. But being able to split up buttons, menus and modals into seperate folders would be a game changer. Otherwise they would all fall under
Where |
Personally I think this would turn CommandKit into some Next.js framework for discord.js, which doesn't make it beginner-friendly as it's currently advertised. |
On Project StructureWe plan to introduce a well-organized project setup that is easy to use over a long period. This is currently under internal discussion to find the best solution.
This idea isn't complex, considering CommandKit's design to automatically handle commands. However, having many |
Would love to see seperate handler paths for buttons, selectmenus, modalsubmits, contextmenus and autocompletes. With the filenames corresponding to the custom ids off those components. e.g.
The text was updated successfully, but these errors were encountered: