How e257-fi/tackler-ng works
Main Components Identification
a) Core Components:
• tackler-core: The main engine containing parsing, processing, and reporting logic
• tackler-api: Public API definitions and interfaces
• tackler-cli: Command-line interface implementation
• tackler-rs: Shared utilities and components
b) External Integrations:
• Git Storage System
• Filesystem Storage
• Configuration System (TOML based)
┌─────────────────────────────────────────────┐
• Client Layer │
• (tackler-cli) │
• ┤
• API Layer │
• (tackler-api) │
• ┤
• Core Engine │
• (tackler-core) │
• ┌─────────────┐ ┌─────────────┐ │
• Parser │ │ Kernel │ │
• ┘ └─────────────┘ │
• ┌─────────────┐ ┌─────────────┐ │
• Filter │ │ Report │ │
• ┘ └─────────────┘ │
• ┤
• Storage Layer │
• ┌─────────────┐ ┌─────────────┐ │
• Git Storage │ │ Filesystem │ │
• ┘ └─────────────┘ │
• ┘
Component Details
• Parser: Transaction parsing (ANTLR-based)
• Kernel: Core processing logic
• Filter: Transaction filtering system
• Report: Report generation (Balance, Register, etc.)
• Git Storage integration
• Filesystem storage
• Input flow: Configuration → Storage → Parser → Kernel
• Processing flow: Kernel ↔ Filter
• Output flow: Kernel → Report → CLI
Key Features to Highlight
Specific callouts for:
• Transaction filtering capabilities
• GIS/Geo-location support
• Multiple report types
• Commodity handling
• Audit functionality
Integration Points
External system connections:
• Git SCM integration
• Configuration file handling
• Input/Output streams
Technical Details
Annotations for:
• Rust implementation
• ANTLR parser usage
• SHA-256 checksum verification
• TOML configuration support