This adds support for the active developer badge on the backend.

The Update DiscordKitCore.swift commit was needed for compilation on my end (with the frontend), you may not need it

This is a non-breaking PR to migrate all uses of OSLog to the cross-platform SwiftLog package. This is done mainly to prepare DiscordKit for life on Linux, and because OSLog wasn't that useful anyways and more troublesome in many ways.

This PR has major changes to the architecture of DiscordKit, to allow supporting bots easier in the future. There are major breaking changes, which are supported by the discordkit-rearchitect branch in Swiftcord.

Performance improvements. Corresponding PR for butter branch in Swiftcord.

Optimisations are not as major as those in Swiftcord, and changes were more to support those made in Swiftcord.

Breaking change: user in gateway cache is now a CurrentUser struct.,

Previously, only the guild ordering user setting was handled. This PR handles some other settings, and stores the whole user settings struct in the gateway cache. It also merges the updated user setting with the old struct when an update event is received since Discord only sends partial user settings in the update event.

This is the corresponding PR in Swiftcord

Handles some events and updates cache with users sent in ready event. Allows proper first-class DM support in Swiftcord.

What changed:

• last_message_id in channels are now updated (allows proper ordering of DMs)
• [Breaking] Cached users are now stored as a [Snowflake: User] dict instead of a [User] array

This PR handles channel and guild gateway events to keep cached data fresh. Please also view the corresponding PR in Swiftcord for more info. This also ensures proper SwiftUI view rendering by calling objectWillChange.send() whenever the cache is modified.

Note: Breaking API changes were introduced, including changing the cached guilds from an array to a [guildID: guild] dictionary. They are relatively minor and should make it easier to use DiscordKit. Please look at Swiftcord for an implementation example.

This PR aims to bring 1st-class bot support to DiscordKit. The checkboxes below outlines what's completed and what's still in the pipeline. The list, as is the bot API, subject to change at any time since this is under intense development and certain parts of the API are still yet to be decided.

Bucket List

• [x] Bot gateway identification with intents support
• [x] Correct user agent, properties and REST authentication
• [x] Sending basic messages
• [x] Event dispatching with NotificationCenter for message create and ready events
• [x] Application command registration with a resultBuilder - supported application command types:
  • [x] chatInput - Slash commands
  • [ ] user - Actions that appear in context menu of users
  • [ ] message - Actions that appear in context menu of messages
• [x] Adding options to commands in the resultBuilder - supported types:
  • [x] subCommand - A "sub-command" with no options
  • [ ] subCommandGroup - A group for nesting other options
  • [x] string - An option accepting a String value
  • [x] integer - An option accepting an Int value
  • [x] boolean - An option accepting a Bool value
  • [ ] user - An option accepting a user as its value
  • [ ] channel - An option accepting a channel as its value
  • [ ] role - An option accepting a role as its value
  • [ ] mentionable - An option accepting a @mention as its value
  • [x] number - An option accepting a Double value
  • [ ] attachment - An option accepting a file attachment as its value
• [x] Handling interactions with a closure, allowing responses
• [x] Support more types of interaction responses
  • [x] Plain content responses
  • [x] Ephemeral responses
  • [x] Embeds
    • [x] Construct fields with a resultBuilder
• [ ] Utility methods for received messages/channels/etc.

Guide

WIP beginner-friendly guide for building a bot with DiscordKit is available!