How andresprograming11/parcial-tienda works
Project type and purpose
• This is a full-stack “shopping cart” application (“Carrito compras”) comprised of:
• A React + Vite SPA (frontend)
• A set of PHP scripts acting as a REST-style API (backend)
• A relational database (implied by conexion.php) storing users and articles
• Purpose: allow end users to browse products, register/login, manage a cart; allow admins to CRUD articles and users.
File structure
• Frontend (root and “Carrito compras” / src):
• src/components: UI building blocks (Navbar, NavbarTop)
• src/views: route-level pages (Productos, Login, Registro, AdminPanel, etc.)
• src/controllers: orchestrate data flow between services & views
• src/services: HTTP clients for each endpoint (articulos, carritoItem, login, registro, gestionar_usuarios, etc.)
• src/routes/AppRouter.jsx: client-side navigation
• vite.config.js, package.json: build & dev config
• Backend (carrito-backend folder):
• conexion.php: DB connection
• login.php, registro.php: auth endpoints
• listar_articulos.php, crear_articulo.php, gestionar_usuarios.php, etc.: CRUD endpoints
• Build artifacts: dist/ (frontend production bundle)
Key architectural insights (README + structure)
• Frontend: React component → view layer; controllers/services abstract API calls
• Backend: procedural PHP scripts exposing JSON endpoints
• Communication pattern: HTTPS REST calls