Probably through GitHub actions. We'll need to spike that.

Who: Library users
What: Create observables that emit on specific IRC messages
Why: So that we don't always have to subscribe to messages() | filter([](m) { return m.command == "COMMAND"; }). Running those filters on every message can become heavy quickly (O(n); n: amount of subscribers).
Points: 5

This is not on a milestone yet, as performance impact hasn't yet been asserted.

Acceptance Criteria

• I can subscribe to something like session.messagesOfType("PRIVMSG").
• That observable would emit whenever a PRIVMSG is received.
• Those observables are kept track of somewhere and get purged when no one's subscribed to a message anymore
• Support for both commands and numerics.

Who: Library users
What: Join channels on an active IRC session
Why: To join channels
Points: 2

Acceptance Criteria

• An API to join a channel is implemented

Technical Discussion

This might go on Irc::IrcSession.

Who: Bot users.
When: A command is posted in chat.
What: Parses the command and finds a suitable handler for it.
Why: So that the bot can accept commands from users.
Points: 5

Acceptance Criteria

• Detects all messages starting with the trigger.
  • That trigger is configured under the "trigger" key of the config file.
• Allows modules to register commands with names and hanglers.
• Looks for and calls that handler when the command is posted in chat.

Example

• Config file contains: trigger: "!".
• A user posts !roll d6.
  The bot should find a command handler for roll and call it with argument d6.

Technical discussion

A command record should contain:

• The command name
• The number of arguments
• A pointer to the handler to call.

When parsing the command, arguments would be split on whitespace until the argument count is reached. If more whitespace is found, it becomes part of the last argument. For example, if command addquote takes 2 arguments, then !addquote somedude My password is hunter2 would be parsed as

command: "addquote"
arguments: ["somedude", "My password is hunter2"]

Depends on: #3
Who: Bot owners.
When: On startup, after logging into the IRC server.
What: Join the channels list in the "channels" key from the config file.
Why: So that the bot can do its job.
Points: 2

Acceptance Criteria

• Automatically joins the channels upon startup