Support non-option free-typed text (or unnamed default option)

[JohnRPB]

Slash command options give users a clear way to navigate bot complexity when the source of that complexity is multiple inputs per command. But what if you want to build a bot that appears to have only one input per command, based on free-typing and natural language processing?

The current approach doesn't seem to work as well because you have to have an option that appears after you type your command which doesn't do anything except reiterate what the command does.

To be concrete, suppose I want to support a user typing:

(A) /new Netflix party on Tuesday at 8 pm

Right now, to get a functional command, the user has to see something like:

(B) /new [event:] Netflix party on Tuesday at 8 pm

where the "[event:]" appears suddenly after they type the first space or is already there if they click on the slash command. I think this is a regression from (A) which non-slash command bots can already do.
It's opinionated towards building based on multiple inputs instead of one diffuse input that may contain many bits.

But the user can already type (A) if the slash command has no options; the only problem is that there's no way to access the non-command text. If there was, I could imagine cool mixing and matching possibilities with options and natural language such as:

(C) /new Netflix Party on Tuesday at 9 pm [description:] let's watch Akira and hang out! [reminder:] 30 min

[VelvetToroyashi]

this is a regression from (A) which non-slash command bots can already do.

I wouldn't say comparing client UI and sending a message is apples to apples, let alone regression; they're not really comparable.

Furthermore, I can see how in some situations having the inline tooltip seems a bit redundant, but I'd personally favor consistency over UX for some semi-specific scenarios