Describe the feature
One very nice QoL feature I think this bot could benefit a lot from is splitting the string by commonly used artist separators (&, x, etc.) if a user puts in multiple artists into the query (something Last.fm obviously doesn't support)
For example: ROSÉ & Bruno Mars - APT. could check if this exists first, and if it gets nothing, split by "&", get ROSÉ, and then be able to show the proper results without having to post an error at all. Realistically, a user is going to end up querying again (thus querying the api again) so it seems logical to me to avoid this step entirely, in cases like this.
More details?
Alternatively, you could just specify in the error a tip on how a user can avoid this, such as saying "make sure you only put the primary artist in the artist name" or something like that, to help avoid this and make people less confused. I know in my server a lot of people were not aware of last.fm using 1 artist only, and found some confusion with pulling up songs.
Code of Conduct
Describe the feature
One very nice QoL feature I think this bot could benefit a lot from is splitting the string by commonly used artist separators (&, x, etc.) if a user puts in multiple artists into the query (something Last.fm obviously doesn't support)
For example: ROSÉ & Bruno Mars - APT. could check if this exists first, and if it gets nothing, split by "&", get ROSÉ, and then be able to show the proper results without having to post an error at all. Realistically, a user is going to end up querying again (thus querying the api again) so it seems logical to me to avoid this step entirely, in cases like this.
More details?
Alternatively, you could just specify in the error a tip on how a user can avoid this, such as saying "make sure you only put the primary artist in the artist name" or something like that, to help avoid this and make people less confused. I know in my server a lot of people were not aware of last.fm using 1 artist only, and found some confusion with pulling up songs.
Code of Conduct