How brazier-dev/hikari-flare works
Main Components
a) Core Component System:
• Sub-components for Buttons, Select Menus, and Modals
• Base Component class hierarchy
b) Context System:
• MessageContext
• ModalContext
• Base Context
c) Event Handling System:
• An "Event Handler" module
• Connection to Hikari's event system
d) State Management:
• Stateless architecture
• How component IDs are utilized for persistence
Relationships and Interactions
• User interaction → Hikari Events → Flare Event Handler → Component Callbacks
• Component Creation → Serialization → Discord API
• State Data → Converter System → Component Storage
Key Technical Elements
a) Integration Layer:
• flare.install(bot) connection point
• Demonstrate how it hooks into Hikari's event system
b) Converter System:
• Converter framework
• Built-in converters (int, str, Literal, Enum)
• Extension points for custom converters
Specific Implementation Details
• Rectangles: Core modules
• Rounded rectangles: Components
• Hexagons: Event handlers
• Diamonds: Decision points for state management
• Blue: Core functionality
• Green: Public API
• Yellow: Event handling
• Gray: External systems (Hikari, Discord)
Important Architectural Notes
• Stateless nature of the system
• How component IDs maintain state between restarts
• Type-safe API design
• Converter system's extensibility
Technical Details
Key Components:
• flare.components.base.py: Base component system
• flare.components/{button,select,modal}.py: Specific implementations
• flare.context/*: Context handling
• flare.internal/event_handler.py: Event processing
• flare.converters.py: Data conversion system