plugin-subcommands "No subcommand was matched"

I'm configuring my subcommand with:

@ApplyOptions<Subcommand.Options>({
    name: "config",
    subcommands: [
        {
            ...
        },
        {
            name: "logs",
            entries: [
                { name: "on", chatInputRun: "chatInputLogsOn" },
                { name: "off", chatInputRun: "chatInputLogsOff" },
            ],
        },
    ],
})

@ApplyOptions<Subcommand.Options>({
    name: "config",
    subcommands: [
        {
            ...
        },
        {
            name: "logs",
            entries: [
                { name: "on", chatInputRun: "chatInputLogsOn" },
                { name: "off", chatInputRun: "chatInputLogsOff" },
            ],
        },
    ],
})

No errors occur, but

/config logs on

/config logs on

(which yes, i have registered) spits out "UserError: No subcommand was matched with the provided command."

Solution

The solution:

 {
     name: "logs",
+    type: "group",
     entries: [

 {
     name: "logs",
+    type: "group",
     entries: [

Jump to solution

log(n)OP•4/15/23, 4:35 PM

WAIT, let me see if it could be a ts5 issue

Favna•4/15/23, 4:38 PM

Silly question maybe but have you called the /register of the plugin?

FFavna Silly question maybe but have you called the /register of the plugin?

log(n)OP•4/15/23, 4:39 PM

Yes, I originally thought this was the issue because I forgot it, but it's there now

Favna•4/15/23, 4:39 PM

Otherwise set debug breakpoints in the JS code in node_modules tbh. Can't really give any other tips seeing as you seem to have covered all bases.

Favna•4/15/23, 4:40 PM

Well other than dumping all code here and me or someone else would do the same but if you can do it yourself it's

A very good learning experience
Saves other people work

FFavna Well other than dumping all code here and me or someone else would do the same b...

log(n)OP•4/15/23, 4:41 PM

I was having issues with my database due to a typescript version (breaking decorator changes), what TS version should i be on?

Favna•4/15/23, 4:45 PM

5 is fine

Favna•4/15/23, 4:45 PM

Just make sure you use the experimental decorator compiler option

Favna•4/15/23, 4:45 PM

Setting those to true uses legacy decorators still

FFavna Well other than dumping all code here and me or someone else would do the same b...

log(n)OP•4/15/23, 4:51 PM

Hmm.. looks like is set to automatically in @sapphire/plugin-subcommands/dist/lib/Subcommand.js:189 which bypasses the check on :192

log(n)OP•4/15/23, 4:51 PM

log(n)OP•4/15/23, 4:52 PM

log(n)OP•4/15/23, 4:55 PM

Am I supposed to explicitly pass type: group?

log(n)OP•4/15/23, 4:56 PM

I am.

log(n)OP•4/15/23, 4:56 PM

That would be my issue!

Solution

Llog(n)I'm configuring my subcommand with: ```ts @ApplyOptions<Subcommand.Options>({ ...

log(n)•4/15/23, 4:56 PM

The solution:

 {
     name: "logs",
+    type: "group",
     entries: [

 {
     name: "logs",
+    type: "group",
     entries: [

Favna•4/15/23, 5:45 PM

Oh haha

Favna•4/15/23, 5:45 PM

Yes

Favna•4/15/23, 5:45 PM

I forgot

Favna•4/15/23, 5:45 PM

Pretty sure the documentation specify that

Favna•4/15/23, 5:45 PM

Well typedoc so on hover

Favna•4/15/23, 5:46 PM

https://www.sapphirejs.dev/docs/Documentation/api-plugins/interfaces/subcommands_src.SubcommandMappingMethod#type

Sapphire Framework

Interface: SubcommandMappingMethod | Sapphire

subcommands/src.SubcommandMappingMethod

Favna•4/15/23, 5:46 PM

Docs say it too