Context Menus vs Application Commands - separate or not?
Question time ❓
Context menus.. they exist. They're like used once a blue century. How should we handle them in Sapphire? Should the split between application commands and context menus be clear (so a function for each), or should they both be in the same function? (especially since the interface is almost 1:1, past the target for context menus)? Should the same be done for preconditions?
vladdy•953d ago
CC @Developers for one
Favna•953d ago
Can a difference be made through command options?
vladdy•953d ago
What do you mean?
UndiedGFX•953d ago
Just like how you would handle slashies?
Because they both are almost same
vladdy•953d ago
So separate function for them?
MC Princess•953d ago
separate function would probs be better
UndiedGFX•953d ago
^
24•953d ago
separate, can't see a reason to morph them together (at lease now)
I also see people separating their menu commands completely from other commands, so it follows what a (normal) person would want to do
𝖄𝖚𝖌𝖊𝖓•953d ago
I would actually consider context menu as new pieces. You can get a message. Or a user. Etc. Kind of different imo
But thats me
I dont consider them commands btw because they aren't really a command. They are an action on something
Instead of some kind of request of the bot. They more like a action for the bot to run on x
vladdy•953d ago
Discord considers them application commands
𝖄𝖚𝖌𝖊𝖓•953d ago
Hmm.
Then its whatever I guess
If we want to stay as close to Discord that is
Otherwise my opinion still stands
vladdy•953d ago
It also wouldn't make sense to make them separate pieces just like how slash commands aren't different pieces
𝖄𝖚𝖌𝖊𝖓•953d ago
True'ish
Welcome to the Sapphire Discord server! The next-gen object-oriented Discord.js bot framework can be found here.
2.2KMembers
View on DiscordWant results from more Discord servers?
More PostsInteraction Handlers after usageWant to give interaction handlers a shot **now**?
Well, you can! Just run the command below and givInteraction Handlers!!Hello peeps!
I know, I know, allllll of you (myself included) are just basically begging me for appInitial Commit ThoughtsI've pushed the initial commit for interaction handlers: heavily wip, totally untested and raw (justThe statefulness or statelessness of Interactions1. Most likely, but it would be a nice addition if I was able to have non-state "callbacks" as mentiInteraction handlers in the command instead of globallyHonestly. I would much rather add interactions from my command and from there tell to continue in (fReply sess 2**1.** Yes. This also follows the design pattern that we more-or-less employ already for Sapphire. Wdont feel like creating a review on GitHub...PR is up: https://github.com/sapphiredev/utilities/pull/152
CC @kyra 🩵🩷🤍🩷🩵 @vladdy