How victsilva37/golazo-rup works
Project type and purpose
• This is a full-stack web application (“golazo-rup”) composed of:
• An Angular single-page application (SPA) in the angular-project directory
• A NestJS REST API backend in the nest-project directory
• A relational database (via TypeORM entities) storing players, categories, and goal statistics
• The domain revolves around “Jugador” (player), “Categoria” (category), and “Estadistica_gol” (goal stats), so the system serves a frontend UI for browsing/managing players and their goal data, while the backend exposes REST endpoints and persists data.
File structure
• Top-level directories:
• angular-project/ → Angular client (app/, components/, layouts/, interfaces/)
• nest-project/ → NestJS server (src/app.module.ts; src/{categoria,estadistica_gol,jugador}/ modules, controllers, services, entities)
• documentacion/ → API documentation text file
• Angular side: component-based architecture (each UI widget under src/app/components), global routes in app.routes.ts, and use of interfaces for typing.
• NestJS side: modular structure (one module per domain entity), MVC-style controllers calling services, with entities for ORM mapping.
• Config/build files: angular.json, tsconfig*.json, package.json at each root, .gitignore, ESLint/Prettier configs, nest-cli.json.
Detail without overthinking
• NestJS module separately to reflect its distinct entity/service responsibilities.
• Angular folder structure by grouping related components and interfaces.