How ab623/goeero works
Main Components
• Client Layer (CLI Application)
• Library Layer (Eero Package)
• External Service Layer (Eero API Service)
Component Details
a. Client Layer (Top):
• Main command interfaces: auth, account, devices, networks, and session
• Session file storage component (eero_session.txt)
b. Library Layer (Middle):
• eero.go (core functionality)
• types.go (data structures)
• This should be shown as the intermediary between the CLI and External Service
c. External Service Layer (Bottom):
• Eero API Service
• Authentication endpoints (Phone/OTP flow)
• Data endpoints (account, devices, networks)
Flow Representations
• CLI → Library (Method calls)
• Library → External Service (API calls)
• External Service → Library (Response data)
• Library → CLI (Processed data)
• CLI → File System (Session storage)
• User Input → CLI → Library → Eero API
• ↓
• Session Storage
• CLI Request → Library → Eero API
• ↓
• JSON Output
Important Elements
• Session token flow and storage
• JSON as the primary data format for responses
• Authentication flow as a two-step process
• Main public methods from the library
• Error handling paths
Technical Details to Note
• Go as the implementation language
• Module dependency structure
• File system interaction points
• HTTP/REST communication with the Eero API