How dev-michaelcruz/api-carros-java-angular works
Project Type and Purpose
• This is a full-stack CRUD web application (“api-carros-java-angular”) with:
• Frontend: Angular SPA (Single Page Application)
• Backend: Java Spring Boot REST API
• Database: relational (initialized via schema.sql)
File Structure
• Top level folders:
• api/ → Spring Boot app
• frontend/ → Angular client
• In api/:
• src/main/java/com/michaelcruz/api/controllers → REST controllers (Carro, Marca, Cor)
• …/services & …/services/impl → business logic
• …/repositories → Spring Data JPA repos
• …/entities → JPA entities
• resources/application.properties & schema.sql → DB config
• In frontend/:
• src/app/components & pages → Angular UI components/pages
• src/app/services → HTTP client services for Carro, Marca, Cor
• src/app/model → TypeScript models
• angular.json, package.json → build config
Key README Insights
• Purpose: demonstrate CRUD operations on “carros”
• Stack: Java + Spring Boot + Angular
Detailed Breakdown of Components
• Frontend zone:
• UI Pages: Home, Lista, Cadastro-Form
• Shared Components: Card-Inicio
• Services: CarroService, MarcaService, CorService
• Models: Carro.ts, Marca.ts, Cor.ts
• Backend zone:
• REST Controllers: CarroController, MarcaController, CorController
• Service Layer: CarroServiceImpl (implements CarroService), MarcaService, CorService
• Persistence Layer: CarroRepository, MarcaRepository, CorRepository
• Entities: Carro, Marca, Cor
• Util: CarroUtil for mapping or DTO logic
• Config: application.properties (DB URL, credentials), schema.sql