Interaction response shows choice value instead of name

[th0mk]

Description

When you add a slash command that has an option of type 3 with pre-set choices, the interaction response shows the value of the choice in the interaction response instead of the name.

Steps to Reproduce

Add a command with an option of type 3.

To that option, add a choice where the name is different from the value.

After you've added this command, use it with the option that has a name different from the value.

Make sure you respond with an interaction response that shows the slash command.

Expected Behavior

The interaction response shows the slash command that has been used together with the options. The choice you pick for an option is shown with their name and not their value.

This also allows other users to simply copy and paste the command and use it again.

Current Behavior

The response shows the choices you make for an option with their value instead of their name.

This also means that the command is invalid when copied and used again, since you can't use the value when using a slash command.

Screenshots/Videos

Add a command like this:

Use the command:

The response shows the command with the choice value instead of the name.

This means that when you copy and paste the example the time period is invalid:

Client and System Information

Canary 73730 (8469559)
Windows 10 64-Bit

[davfsa]

This should probably go to the bug-hunters discord as this is not really API related. https://discord.gg/discord-testers

[GitSparTV]

I think it's better to accept both choices name and value. You can type both Half-yearly (last 6 months) and half.

[msciotti]

Coming back to this after what, funny enough, was a long discussion. Not months long, but long.

This is working as intended, though I also don't like it. That string you're referencing is the raw value being sent to our servers. We would actually have to do some additional fetching of command data on the server to match value back to name and send it to our clients. Closing this for now, but tracking internally.

[Sylveondev]

alright boys. This issue is resolved. Discord is working as intended now.