A single filterable select instead of four.

[Mehgugs]

Instead of four arbitrary combinations of types, a single "filtered select menu" should be available.

The following ordering of enums, field names, and other fine details are to illustrate this idea and are not part of the suggestion itself

Example select inclusion enum:

USER = 1 << 1
ROLE = 1 << 2
CHANNEL = 1 << 3
...

Example select payload

{
   "type": FILTERED_SELECT,
   "include": 10 //This includes users and channels according to the above enum
   "channel_types": [0], //Since we're including channels this option works
   // ...etc
}

This would make it much easier to use these selects, and would allow for future types to be included without a new type being created. I'm honestly not sure why this wasn't the current implementation.

An immediate use case for this is being able selects with combinations of types not arbitrarily chosen by discord.

EDIT:
In case it was immediately clear from the original post, another feature of this proposal would be the ability to extend this type with new enum members. To add guild support the api only needs to have a new enum member added with any associated fields. Since this is a purely additive change (adding new json fields does not break existing code) it would be a much easier to add support to libraries.

[Shepard]

The current types don't feel like arbitrary combinations to me at all.
Do you have a use case for different combinations?

[MinnDevelopment]

[Mehgugs]

I wanted a user | channel option as a message target. Requiring users to have a certain role is another feature I think has been requested which would make that even better.