How paulluqueccosi/borrar_2 works
Project Type & Purpose
• Full-stack (front-end heavy) Single-Page Application built with Angular 18
• Purpose: A subscription-based filter tool (“SwiftSelect”) with user authentication, plan management (Stripe), Google Drive integration, and a marketing landing section
• Generated via Angular CLI; deployed as static assets served by Nginx (see deploy/swiftselect.io.conf)
File Structure
• src/app
– features/…: feature modules (auth, configuration, filter, landing, profile) each with their own routes, components, pages, guards, services
– core/: global services, interceptors, constants, directives, validators and shared utilities used by all features
– shared/: reusable UI components, directives, pipes, layouts
– app.component, app.routes, app.config, bootstrapping (main.ts)
• src/environments: per-environment API URLs, feature flags
• deploy/: static files including service worker and robots/sitemap
• build config: angular.json, tsconfig.json, Tailwind via postcss.config.js
README Insights
• Angular CLI workflow: ng serve, ng build → dist/
• Unit tests (Karma), e2e tests
• Deployment scripts reference QA/PM2/LLM-worker (backend LLM microservice)
Main Components & Interactions
a. Browser (Client)
– Loads index.html → main.ts → AppModule
– Renders feature modules via Angular Router
– UI components consume core/shared services
b. Angular Application
– Feature Modules (auth, filter, configuration, landing, profile)
– Core Module
• HTTP Interceptors (auth-token, loader, error handling, backend URL override)
• Services (AuthService, StripeService, GDriveService, FilterService, etc.)
• Constants (API endpoints, app constants)
– Shared Module (UI library: reusable components, directives, pipes, layouts)
c. HTTP/API Layer
– Outbound API calls via Angular HttpClient
– Base URL from environment config
– Interceptors append JWT, handle errors, show loader
d. Backend Services (external to this repo)
– Authentication & User Management API
– Filter Engine API (calls LLM Worker via PM2)
– Subscription & Payments API (Stripe Platform)
– Google Drive API
e. External Systems
– Stripe (checkout, sessions)
– Google Drive
– LLM Worker (swiftselectllm-worker.service)
f. Deployment
– Angular CLI build → dist/ → served by Nginx
– Static assets + service worker (PWA) via deploy/static config file
Architectural Patterns & Principles
• Modular Angular architecture (feature modules + Core/Shared)
• Dependency injection for services
• Router + lazy loading for feature modules
• HTTP interceptor pipeline
• Environment-based configuration
• PWA service worker integration