How estebanrcarmona/planning-pocker-angular works
Project type and purpose
• This is a front‑end single‑page application (SPA) built with Angular.
• Purpose: Provide an interactive “Planning Poker” estimation tool using Atomic Design for UI components, allowing users to join sessions, pick Fibonacci cards, reveal selections, and calculate an average.
File structure
• Top‑level config files: angular.json, tsconfig*.json, jest.config.js, karma.conf.js
• src/app: contains all Angular modules, components, and service implementations
• components/atoms → smallest UI building blocks (buttons, cards, inputs, toasts)
• components/molecules → composed UI pieces (create‑game form, table display)
• components/pages → route‑level views (create‑game, game session, pre‑load, register)
• shared/services → business logic and API/communication layers (GameService, communicationService, toastService, validators)
• shared/interfaces & Constants → type models and global constants
• src/environments: environment.ts / environment.prod.ts for runtime configuration (API endpoints, feature toggles)
• Testing setup: *.spec.ts alongside every component and service, Jest + Karma config
• No backend code in this repo—interacts with an external RESTful API (and possibly WebSockets via communicationService)
README for additional insights
• Confirms Angular + TypeScript + semantic HTML + CSS
• Mentions RESTful API integration “if applicable” (Game sessions backend)
• Emphasizes Atomic Design, responsive layout, accessibility
Elements
• UI → Services (HTTP call) → REST API
• UI ← Services ← API response
• UI ↔ communicationService ↔ WebSocket server
• UI components (blue)
• Services (green)
• External systems (orange)
• Labels: method names (e.g. GameService.getGame(), communicationService.connect())
Tips
• UI components visually by Atomic Design tiers.
• Routing transitions (e.g. Register Page → Create Game → Game Session).
• Environment injection for API base URL.