How tyrrrz/discordchatexporter works
Project type and purpose
• DiscordChatExporter is a cross-platform client application (desktop GUI and CLI) that exports message history from Discord channels.
• It’s organized as three main deliverables:
• DiscordChatExporter.Gui – the Avalonia-based desktop UI
• DiscordChatExporter.Cli – the command-line interface
• DiscordChatExporter.Core – the shared library containing domain models, Discord API client, exporters, filters, and format writers
High-level layers & components
• Presentation Layer
• CLI (Program.cs + Commands/*)
• GUI (App.axaml, ViewModels/*, Views/*, Services/*)
• Application Layer
• Command handlers (ExportCommandBase, DiscordCommandBase)
• DialogManager, ViewManager, SettingsService, UpdateService
• Domain/Core Layer
• DiscordClient (HTTP wrapper over Discord REST API)
• Data models under Discord/Data (Message, Channel, Guild, User, Embeds, etc.)
• Exporting pipeline (ExportContext → MessageExporter → format‐specific writers: CsvMessageWriter, HtmlMessageWriter, JsonMessageWriter, PlainTextMessageWriter)
• Filtering (MessageFilter AST, grammar parser)
• Partitioning (FileSizePartitionLimit, MessageCountPartitionLimit)
• Markdown parsing/rendering (MarkdownParser, MarkdownVisitor, HtmlMarkdownVisitor)
• Infrastructure Layer
• HTTP utilities (in Core/Utils/Http.cs)
• File system & path utilities (PathEx, UrlBuilder)
• Docker support (dockerfile, docker-entrypoint.sh)
• CI/CD (GitHub workflows, Dependabot)
External dependencies & services
• Discord’s REST API (HTTPS endpoints) – the data source
• Local file system – export destination
• Docker hub – optional containerized CLI
• GitHub Actions – build/test/release pipeline
Diagramming guidance
a. Main components to represent
– User (actor)
– CLI UI & GUI UI
– Command/Controller modules
– Core library (DiscordClient, Export pipeline, Filters, Writers)
– Discord REST API (external service)
– File system (local storage)
– CI/CD pipeline (optional – GitHub Actions, Docker)
b. Relationships & data flows
1. User → CLI or GUI (input triggers)
2. CLI/GUI → Command Handler → Core API
3. Core → DiscordClient → Discord REST API (HTTP request/response)
4. Core → ExportContext → MessageExporter → Writers
5. Writers → File system (writes export files)
6. GUI may invoke UpdateService to check GitHub Releases
c. Architectural patterns & principles
– Layered architecture (Presentation → Application → Domain → Infrastructure)
– Command pattern for CLI commands
– Dependency inversion: Core library does not depend on UI
– Single Responsibility: separate classes for data models, exporting, filtering, rendering
d. Key technologies & frameworks
– C#/.NET 6+
– Avalonia UI (GUI)
– Spectre.Console.CommandLine or similar for CLI binding
– Razor templates (.cshtml) for HTML Preamble/Postamble
– Superpower-based parser for filters & markdown
– GitHub Actions for CI/CD, Docker for containerization