Extend the "ban user" endpoint to accept "login" as an alternative to the already existing "user_id"
Today when you're using chat you can just enter
/ban user and the user will be banned, and the same is true for the IRC command, you can ban just by their username. It would be good if the ban endpoint would follow the same pattern.
The use case for that is that I have a tool to mass-ban multiple users on multiple channels at the same time (I mod quite a lot of channels, so this streamlines this process), and I decided to migrate from the IRC API to the helix API, but because of it just accepting the user_id, now I have to do an additional request to get their ids first (or multiple requests, if there are more than 100 users), which is inconvenient, but the real problem is:
- I can't ban users which are suspended/deactivated anymore cause I don't know their id, and the get users endpoint just returns that the user does not exist when they are suspended/deactivated (even though they do exist, and could be unsuspended/deactivated at any time). Even though they are suspended, I still want to ban them, as I can't know if the suspension is temporary or permanent, or if the user will just reactivate the account sometime later.
I feel like being able to just pass the login to that endpoint would make the whole process a lot easier and faster (and also, it would save a few requests to get their ids)