Allow choices to be set such that the server is polled for choices instead of being statically set

[ckohen]

Description

The choices array on ApplicationCommandOption is statically assigned at creation time. There are some use cases where it provide much better UX by allowing choices to be dynamically fetched from the server, e.g. as the in-built /giphy does.

Note: this is not suggesting to remove the existing static choices set, rather to augment them where needed.

Why This is Needed

While many commands function very well with statically defined choices for options, some commands would greatly benefit both on the server side and from a UX perspective if these option could be dynamically updated.

Alternatives Considered

• The current way of handling this, which is to not provide a choices array at all and let the users know through other means which choices are currently valid
• Provide a full list of possibly valid choices that are statically assigned, and error when the choice selected is invalid at that time

Additional Details

As an example for where I would be using this type of choice: I have a room management system. Users can create, join, set properties on rooms. These are associated with an id on the back end so names can be descriptive and user settable. Currently this command tells users the names of rooms and their associated id's, then they must input said id into the relevant commands. Dynamic choices would allow setting an integer type with the associated name as "name" and the id as "value" to create a much better user experience.

Ideally, this would be implemented as another InteractionType so that data can even be filtered farther based on the guild / channel / member and can follow the same 3 second expiry behavior.

I would understand if this is not feasible to implement at this time, but I urge consideration for long term UX improvements.

[ckohen]

Note: This is not officially out yet, but is implemented and being documented as noted here #3849

[Lulalaby]

Yes :3