How felangga/chiko works
Main Components Identification
The project is a standalone application with these key components:
a. Core Components:
• gRPC Controller: Handles all gRPC-related operations
• UI Layer: Manages the Terminal User Interface
• Storage Controller: Handles file operations and bookmarks
• Entity Layer: Contains core data structures
Architectural Pattern
The project follows a clean architecture pattern with clear separation of concerns:
• Controller Layer (pkg/controller)
• UI Layer (pkg/ui)
• Entity Layer (pkg/entity)
• Terminal UI |
• (tview-based interface)|
• gRPC Controller |
• Bookmark Controller |
• Storage Controller |
• gRPC Services |
• (External Connections) |
Component Relationships
• UI Layer → Controllers (Command flow)
• Controllers → External gRPC Services
• Controllers → Local Storage
• Entity objects flowing between components
Specific Component Details
UI Layer Components:
• Bookmark Menu
• Log List
• Output Panel
• Sidebar Menu
• Modal Windows (Authorization, Metadata, Request Payload)
Controller Components:
• gRPC Controller
• Connection handling
• RPC invocation
• Sample generation
• Bookmark Controller
• Save/Load operations
• Migration handling
• Storage Controller
• File operations
• Working directory management
Entity Components:
• App configuration
• Authentication
• Bookmarks
• Logs
• Metadata
• Sessions
• Themes
Important Flows to Highlight
Key workflows with numbered sequences:
Technical Details
Annotations for:
• grpcurl integration points
• tview UI component connections
• File storage locations
• Configuration paths