How aura-nw/aurascan works
This project is a large, feature-rich Angular application named AuraScan. Its purpose is to allow users to track wallets, active users, and blockchain-related statistics. The codebase is organized as a full-fledged, client-side frontend using Angular CLI (version 16) that leverages modular design principles and uses deployment tooling (Docker, Nginx) and CI pipelines (GitHub workflows) to ensure quality and ease of delivery.
Main components of the system
• Frontend Application: The core is built using Angular. It includes layers like pages (for account details, blocks, contracts, proposals, etc.), shared components (cards, dialogs, paginators, notifications, etc.), and global modules (layouts, shared modules, material module).
• Modules & Layers: The project is split into various modules such as “pages”, “core”, “layouts”, “shared”, and “assets”. Each plays a distinct role in user interface, business logic, styling, and external configuration.
• Deployment & CI/CD: The repository includes Dockerfile(s), Nginx configuration, as well as dedicated CI folders and GitHub workflows that facilitate automated testing and build procedures.
• External Integrations & Libraries: There are utility modules (like those in “cosmoskit”, “ethers”, “signing”) which suggest integrations with blockchain networks. These facilitate wallet connection, crypto operations, or blockchain-specific interactions.
Architectural patterns and design principles
• Modular Design: The separation into pages, core services, layouts, and shared modules is indicative of a modular architecture.
• Layered Approach: The clear division between UI, business logic, and infrastructure makes it easier to understand dependencies and data flow.
• Dependency Injection: Angular’s DI is used extensively across services and components to manage dependencies and maintain separation of concerns.
• CI/CD and Containerization: Use of Docker and automated workflows signals a commitment to continuous integration and deployment.
Specific elements
• Labeled Components: All major modules (Frontend, Core, Shared, Deployments, External APIs) should be clearly labeled.
• The flow of data from UI components to core services.
• How core services interact with external APIs.
• The build and deployment pipeline from source code → CI/CD → Docker Image → Nginx serving the application.