How sistemasvillaallende/tasa_front works
Project Type and Purpose
• This is a front-end single-page application (SPA) built with React and TypeScript, using Vite as the build tool and Tailwind/PostCSS for styling.
• Purpose: “Aplicación de Tasa a la propiedad” – a property-tax management interface (user authentication, listing/consulting “cedulones,” handling payments, reports, etc.).
• All code lives under src; there is no in-repo backend. The app likely communicates with external REST endpoints (configured via .env.prod) or uses local JSON mocks.
File-Structure Analysis
• Top-Level:
• index.html + public/ → static assets entry point
• vite.config.ts, tsconfig*.json, tailwind.config.js, postcss.config.js → build/config
• package.json → dependencies/devtools
• .env.prod → production API endpoints
• src/:
• assets/ → CSS, images, JSON fixtures
• base-components/ → reusable UI primitives (buttons, form controls, CKEditor wrappers…)
• components/ → domain-specific components (header, invoice, menus…)
• layouts/ → page layout wrappers (side menu, top menu, simple menus…)
• pages/ → route targets, grouped by feature (Tasa, CtasCtes, Deudas…)
• router/ → React-Router setup
• stores/ → Redux slices + store configuration
• context/ → React Context providers (User, Tasa, Cedulones)
• utils/ + modules/ → helper functions, API wrappers, secure storage
• interfaces/ + types/ → TypeScript models and declarations
Key Architectural Patterns
• Component-Based: all UI is broken into base-components → components → pages.
• State Management: hybrid of React Context (for domain-specific state) and Redux Toolkit slices (global UI state like menus, darkMode, checkout).
• Build & Deploy: Vite bundles TSX + CSS into static assets; served by a static host (S3, Netlify, CDN) or by an external web server.
• External Integrations: REST API (env vars), CKEditor, Google Maps loader, third-party CSS/JS libs (TomSelect, TinySlider).