Slash vote

[benetherington]

DRAFT: pretty close to being done. I've done a quick "looks like it works" test on Discord.

To do:

• Re-read and possibly refactor.
• Figure out the frontend design.
  • Right now, I just have buttons stacked up in messages (no event handler, thus the fail message in screencap.) This results in n/5 replies, but still, the buttons are SHUJ.
  • Usernames will never resolve in buttons, but that's sensible; they can't become links. Change what values get pulled out of the DB.
  • Text markup doesn't work on buttons. K thx Material Design.
  • I'd really like these buttons to look like the insta-vote buttons (ie resolved username, suggestion with code styling, and a single (#) VOTE button.
  • We can't put markup text elements in MessageActionRows, so we'd have to issue individual replies for each suggestion. As is, ten buttons on their own row take up an entire screen, I think n/1 replies are not acceptable.
  • Two buttons on each row gets us down to n/6, but they'll start to wrap for long suggestions.
• We only have three seconds to reply to an interaction event. Will that always be enough, or should we interaction.deferReply()?
• Fix sub-command. The top level command is not callable, it's behaving like a command group.

[benetherington]

Okay, I kind of hate looking at this now. I've re-tooled it a million times just trying to get the dammed thing to look right, and Discord really doesn't want to play nice. I'd be happy if you at least tore this to shreds and let me make the CODE look nice!

[fonji]

Hi Ben! I'm sorry I'm not able to review code right now. Tests says it's not covid, either they're wrong or it's good ol' dumb flu.

[benetherington]

Oh no! Get better soon! I hope you're not feeling too poorly!

[benetherington]

Branch vote-button now contains all changes included in this PR.