How brunobriante/rodanodeck_bot works
Main Components
a. Entry Point Layer:
• cmd/bot/main.go as the application entry point
b. Core Bot Layer:
• Center the internal/bot package as the core of the system
• Following components from internal/bot:
• bot.go (main bot logic)
• protondb.go (ProtonDB API integration)
• results.go (results handling)
• sdhq.go (Steam Deck HQ integration)
• steam.go (Steam API integration)
c. External Services Layer:
• ProtonDB API
• Steam API
• Steam Deck HQ API
• Bot Platform API (likely Telegram or Discord)
d. Configuration Layer:
• Configs directory with env.go and message.tmpl
• Configuration flow into the system
Component Relationships
• Entry Point → Bot Core (initialization flow)
• Bot Core → External Services (API calls)
• Configuration → Bot Core (config injection)
• Bot Core → Results Handler (data processing)
Specific Implementation Details
[External Services Layer]
• ↕
[Bot Core Layer]
• ↕
[Configuration Layer]
• ↑
[Entry Point Layer]
b. Specific elements:
• Message flow from user input through the system
• API call patterns to external services
• Results processing and response flow
• Configuration injection points
Technical Details to Highlight
• Go-specific patterns (goroutines if used)
• API integration points
• Configuration management
• Message template system