Optional Interaction Endpoint URL override configured at the slash command level

[bennebbenneb]

In addition to using a different endpoint for the command, the options should be at the level of the command. so no needing to traverse through the nested options and no need to update the codebase when refactoring a group name.

{
  "name": "config",
  "description": "Customize.",
  "options": [
    {
      "name": "server",
      "type": 2,
      "description": "Customize server.",
      "options": [
        {
          "name": "matchmaking",
          "type": 1,
          "description": "Customize matchmaking for you server.",
          "url": "INTERACTION_ENDPOINT_URL",
          "options": [
            {
              "name": "visibility",
              "description": "Matchmaking Visibility.",
              "type": 3,
              "choices": [
                {
                  "name": "Public (Default)",
                  "value": "public"
                },
                {
                  "name": "Private",
                  "value": "private"
                }
              ]
            }
          ]
        }
      ]
    }
  ]
}

[Mehgugs]

I think this is something you can do today with any gateway service you like. Adding this here would bloat the payload and potentially impact future features.

[bennebbenneb]

the options in the payload currently looks like this

{
    "options": [
      {
        "name": "server",
        "options": [
          {
            "name": "matchmaking",
            "options": [
              {
                "name": "visibility",
                "type": 3,
                "value": "public"
              }
            ],
            "type": 1
          }
        ],
        "type": 2
      }
    ],
}

With my change the payload options would look like this

{
  "options": [
    {
      "name": "visibility",
      "type": 3,
      "value": "public"
    }
  ]
}

So the payload would actually be smaller for every invocation. The initial configuration payload would be bigger, but that only runs once so no need to worry about that.

[bennebbenneb]

I have a partial solution to fix the coupling between group/subgroups and slash commands. The one drawback is that each slash command name needs to be unique. So you can't have a command structure like this since both use kick.

/bot kick id:@somebot
/member kick id:@somemember

const x = {
    "options": [
        {
            "name": "server",
            "options": [
                {
                    "name": "matchmaking",
                    "options": [
                        {
                            "name": "visibility",
                            "type": 3,
                            "value": "public"
                        },
                        {
                            "name": "voice-channels",
                            "type": 3,
                            "value": "enabled"
                        }
                    ],
                    "type": 1
                }
            ],
            "type": 2
        }
    ]
}

const cleanOptions = options => !options.options[0].options ? options : cleanOptions(options.options[0]);

console.log(cleanOptions(x))

// {
//   "name": "matchmaking",
//   "options": [
//     {
//       "name": "visibility",
//       "type": 3,
//       "value": "public"
//     },
//     {
//       "name": "voice-channels",
//       "type": 3,
//       "value": "enabled"
//     }
//   ],
//   "type": 1
// }