How magdalenaszym/ludoteca-react works
Project type and purpose
• This is a full-stack “ludoteca” (game library) management application.
• Frontend: a React/TypeScript SPA that manages games, authors, categories, customers and borrows.
• Backend: a Spring Boot service exposing CRUD REST endpoints, persisting to an in-memory H2 database.
File structure
• Top level:
• ludoteca-react/ → React frontend
• tutorial/ → Spring Boot backend
• Frontend:
• public/index.html, src/main.tsx → app entry point, bootstrapped via Vite
• src/components, src/pages → UI components, page layouts per domain (author, game, customer, category, borrow)
• src/redux/services/ludotecaApi.ts → Redux Toolkit Query service for HTTP calls
• src/redux/features/messageSlice.ts → global messaging state
• src/context/LoaderProvider.tsx → loading‐indicator context
• Backend:
• src/main/java/com/ccsw/tutorial → Spring Boot app package
• controller/ → REST controllers per entity
• service/ + serviceImpl/ → business logic layer
• repository/ → JPA repositories
• model/ → JPA entities and DTOs
• common/criteria & pagination → custom search/paging abstractions
• config/ModelMapperConfig → DTO↔entity mapping
• resources/application.properties + data.sql → H2 config and seed data
README
• Confirms tech stack: React+TypeScript on the front, Java 17 Spring Boot with JPA/Hibernate and H2 on the back.
Detailed coverage
• Integration points: API service endpoint URLs, model mapping, search specifications.
• Build/deploy context (Vite dev server, Maven) if relevant to the engineering discussion.