Slash Command string still required, even when `min_length` is set to `0`

[tyrantlink]

Description

This could be deliberate, but given that min_length can be set to 0, this seems like a bug.

Slash Command string options, with required set to True and min_length set to 0, require a value to be specified, even though min_length is 0

Steps to Reproduce

Create a Slash Command, with a string option, with required set to True and min_length set to 0

example json

{
    "type": 1,
    "name": "send",
    "description": "send a message",
    "options": [
        {
            "type": 3,
            "name": "message",
            "description": "message to send",
            "required": true,
            "min_length": 0
        }
    ]
}

Expected Behavior

The option is valid, even with an empty value, returning an empty string "" to the bot

Current Behavior

The option is invalid, value must be specified

Screenshots/Videos

Client and System Information

Web Stable 345368 (24ebc65) Build Override: N/A Fedora Linux 40 (Silverblue) x86_64

[Nixill]

I would expect this to work for a bot to be able to have an option that is presented to the user (as if required, not in the optional section), but can be submitted empty. The advantage to this is that the text input would automatically be in the field when the command is entered, rather than the user having to manually select the option before beginning to input a value.

I would also expect that an empty string option like this would be presented in the interaction response object as a value of empty string, rather than omitted from the payload or null.