13 starboard

[Plyb]

Resolves #13

[Plyb]

I made a significant architecture change by adding the concept of reaction handlers. Instead of all reaction handling being done in messageReactionAdd.ts, that file now simply calls the execute message on separate ReactionHandlers. So duplicating reactions was pulled out into its own handler and starboard reaction handling is also in its own handler. In addition, there is a separate messageReactionRemove.ts. Both of these can consume reaction handlers, so we can reuse the starboard reaction handling for both.

[ZYancey]

Looks good!

[AverageHelper]

K I'm gonna look at this today finally

[AverageHelper]

Additional considerations:

• Do we want reactboard messages to be deleted when their original message is deleted? Or are reactboards a deletion-resistant museum of sorts?
• The bot occasionally joins reacts, but it ignores :star: reacts. It should probably ignore all other reactboard emojis, too. We can probs add this later, since right now we only really need the starboard working.

[AverageHelper]

Last comments and then I think it's ready:

[AverageHelper]

Should this file be called index.ts instead, following the pattern in src/events/?

[AverageHelper]

Feels weird for the 'messageReactionRemove' event to execute allReactionHandlers, instead of just a remove handler..

[AverageHelper]

For clarity:

Suggested change

	throw new UserMessageError('React option must be a valid reaction');
	throw new UserMessageError('React option must be a valid emoji');

I don't think you can send a "reaction" as a command argument per-se, but emojis are fair game :P

[AverageHelper]

Ideally this would say something different depending on whether the board was created or updated or destroyed, but since we don't differentiate that rn, more generic language might be best:

Suggested change

	await replyPrivately('Reactboard created!');
	await replyPrivately('Reactboard set!');