Localized Aliases

[s5bug]

My old bot system supported both c!タイム and c!時刻 for relaying a user's time under ja-JP.

Slash commands do not even support a fraction of this feature: I would have been alright with naming the command タイム and emplacing 時刻 in its description, but when entering slash commands, descriptions are not searched.

I am proposing an additional field to the application command object:

 {
   "name": "command.time.name",
   "type": 1,
   "description": "command.time.description",
   "name_localizations": {
     "en-US": "time",
     "ja-JP": "タイム"
   },
+  "name_aliases": {
+    "ja-JP": ["時刻"]
+  },
   "description_localizations": {
     "en-US": "Display your or another user's current time",
     "ja-JP": "ユーザーさんか他のユーザーの時刻を見せる"
   },
   "options": [

This way there is still a standard way of typing a command (to be used for documentation or otherwise) and the commands themselves aren't duplicated in the command list.

The aliases could be cleanly displayed in the area marked red:

[Mehgugs]

The developers don't want to add aliases but I'm not sure there's a concrete reason for this stance posted anywhere.

[advaith1]

unfortunately fuzzy matching doesn’t seem to be happening soon, and there are still other use cases for aliases.

[NovaFox161]

Yeah. It's really unfortunate that it's been nearly 2 years and we still don't have even fuzzy matching, making one of the biggest use cases for aliases still unresolved. And as we saw mentioned in that thread and now this, there's plenty of other use cases for aliases as well as established patterns like tags/similar key words

[s5bug]

As far as I can tell, the fuzzy-matching only covers English :)

[NovaFox161]

We don't have fuzzy matching. Just substring matching so /an will match /ban for example

[Mehgugs]

That dev comment is largely hinged on a moot point. There is no reason to assume aliases would be displayed in chat as the command name used or even sent to applications. The search process could resolve all that before the client sends the interaction. Issues with clutter in the picker are problems that need to be fixed in the picker and are not caused singularly by aliases.