Server Companion + Community SDK Integration

[Arlodotexe]

WindowsAppCommunity.Sdk

At Implementing event stream handlers WindowsAppCommunity/meta#12, you'll find Implementing event stream handlers WindowsAppCommunity/meta#12, which (when fully expanded) has a tree that looks like this:

• Assessing and planning MVP event stream handler implementations WindowsAppCommunity/meta#14
  • Planning and tracking implementation of "Root" event stream handlers WindowsAppCommunity/meta#16
    • Planning and tracking implementation of "Publisher" event stream handler WindowsAppCommunity/meta#19
    • Planning and tracking implementation of "User" event stream handler WindowsAppCommunity/meta#20
    • Planning and tracking implementation of "Project" event stream handler WindowsAppCommunity/meta#18
  • Planning and tracking implementation of "Virtual" event stream handlers WindowsAppCommunity/meta#17
    • Planning and tracking implementation of "Accent Color" event stream handler WindowsAppCommunity/WindowsAppCommunity.Discord.ServerCompanion#22
    • Planning and tracking implementation of "Connections" event stream handler WindowsAppCommunity/WindowsAppCommunity.Discord.ServerCompanion#23
    • Planning and tracking implementation of "Entity" event stream handler WindowsAppCommunity/WindowsAppCommunity.Discord.ServerCompanion#24
    • Planning and tracking implementation of "Link collection" event stream handler WindowsAppCommunity/WindowsAppCommunity.Discord.ServerCompanion#25
    • Planning and tracking implementation of "Project role collection" event stream handler WindowsAppCommunity/meta#27
    • Planning and tracking implementation of "Publisher role collection" event stream handler WindowsAppCommunity/WindowsAppCommunity.Discord.ServerCompanion#26
    • Planning and tracking implementation of "User role collection" event stream handler WindowsAppCommunity/meta#27
    • Planning and tracking implementation of "Images collection" event stream handler #28

These tickets are all closed off, and the SDK is read to be integrated with our Discord bot.

Initial approach

The CLI serves as an example of how to implement our SDK in our Discord bot, but it will look slightly different.

There are many things we'll need to consider to improve the overall user experience here.

Understanding how the SDK integration with our Discord Bot will look different to the command-line interface is our first step here.

Getting started

The below is the preferred order to handle implementation in:

• CLI to Slash commands (with autocomplete)
• Backlinking and invite system
• User isolation (ready) + flexible permissions system (TBD)

CLI to Slash Commands

See: #23

Backlinking and Invites

See: #24

Isolating users

See: #25

Flexible user permissions

See: #26

Discord Role Migration

See: WindowsAppCommunity/meta#27