AsuraPadel
Padel management system where I was the primary Angular web developer. The authenticated area contains 8 screens: home, dashboard, ranking, points marketplace, products, seasons, members and plans. The frontend uses standalone components, typed HTTP services and centralized interceptors for API integration.
- Context
- Padel management system with the Angular frontend and backend in separate repositories. My main responsibility was Angular web development.
- Pressure
- Bring registration, queries and points features together in an API-connected interface, with loading and error handling for operations.
- Decision
- Organize the frontend by feature, use standalone components and typed HTTP services, and centralize API integration through interceptors.
- Evidence
- 8 child routes in the authenticated area; standalone components; services with typed DTOs; authentication and base URL interceptors registered with HttpClient; a member update test checking the PUT method, request body and HTTP response.
- Impact
- Implemented frontend scope: 8 screens in the authenticated area, covering home, dashboard, ranking, points marketplace, products, seasons, members and plans.