How zalapanda/redmine-time-spender works
Project Type Analysis
This is a Chrome browser extension that interfaces with Redmine for time tracking, featuring local storage, encryption, and UI components.
Main Components
A. Browser Extension Components:
• Popup Interface (Entry point)
• Background Service
• Options Page
• Content Scripts (if any)
B. Data Layer:
• IndexedDB Storage
• Encrypted Cache
• Cookie Storage (for encryption key)
C. External Systems:
• Redmine Server
• Redmine API
Component Organization
[Chrome Browser Environment]
• UI Layer
• Popup Interface
• Time Entry Management
• Issue Management
• Task Management
• Options Page
• Business Logic Layer
• Background Service
• API Interfaces
• Crypto Service
• Data Layer
• IndexedDB
• Cookie Storage
[External]
• Redmine Server
Specific Implementation Details
A. UI Components (Rectangle with rounded corners, Blue):
• App.tsx
• Bar.tsx
• Dialog.tsx
• EditEntry.tsx
• EditIssue.tsx
• EditTask.tsx
• Atomic Components (atoms/)
B. Services (Hexagons, Green):
• background.ts
• apis/redmine.ts
• apis/crypto.ts
• apis/database.ts
• IndexedDB
• Cookie Storage
• Redmine Server
• User interactions → UI Components
• UI Components → API Services
• API Services → Storage
• API Services → Redmine Server
• Background Service ↔ Storage
• Background Service ↔ Redmine Server
Important Notes
A. Security Flow:
• Encryption/decryption flow
• Where the encryption key is stored and how it's used
• Encrypted vs. non-encrypted data paths
B. Caching Mechanism:
• Flow of data from Redmine to local storage
• What data is cached (projects, issues, activities)
• Refresh/sync mechanisms
C. Key Features to Highlight:
• Time entry management
• Project/issue filtering
• Auto-refresh mechanism
• Search functionality
• Issue creation flow