Implement Core Business Logic APIs for Booking and Technician Management

[Copilot]

This PR implements the complete core business logic APIs for the TechCare platform, providing comprehensive booking and technician management functionality.

🚀 New Features

Booking Management System

• Complete CRUD operations for service bookings
• Role-based access control (Customer, Technician, Admin)
• Status tracking with 6 states: PENDING, CONFIRMED, IN_PROGRESS, COMPLETED, CANCELLED, REJECTED
• Service categorization with 10 predefined categories (COMPUTER_REPAIR, LAPTOP_REPAIR, etc.)
• Advanced filtering by status, category, date range, and search terms
• Pagination support for large datasets

Enhanced Technician Management

• Public technician directory with filtering and search capabilities
• Availability management system for technicians
• Weekly scheduling with day/time slot management
• Technician-specific booking tracking
• Profile management with specialization and rate information

🔧 Technical Implementation

New Database Models

-- Booking model with comprehensive fields
CREATE TABLE "bookings" (
    "id" SERIAL PRIMARY KEY,
    "customerId" INTEGER NOT NULL,
    "technicianId" INTEGER,
    "title" TEXT NOT NULL,
    "description" TEXT NOT NULL,
    "category" "ServiceCategory" NOT NULL,
    "status" "BookingStatus" DEFAULT 'PENDING',
    "scheduledAt" TIMESTAMP(3),
    "location" TEXT NOT NULL,
    -- Additional fields for pricing, notes, tracking
);

-- Technician availability for scheduling
CREATE TABLE "technician_availability" (
    "technicianId" INTEGER NOT NULL,
    "dayOfWeek" INTEGER NOT NULL,
    "startTime" TEXT NOT NULL,
    "endTime" TEXT NOT NULL,
    "isAvailable" BOOLEAN DEFAULT true
);

API Endpoints (15 total)

Booking Management:

• POST /api/v1/bookings - Create booking (customers)
• GET /api/v1/bookings - List bookings with filters
• GET /api/v1/bookings/:id - Get booking details
• PUT /api/v1/bookings/:id - Update booking
• PUT /api/v1/bookings/:id/status - Update status
• PUT /api/v1/bookings/:id/assign-technician - Assign technician (admin)
• DELETE /api/v1/bookings/:id - Cancel booking

Technician Management:

• GET /api/v1/technicians - List available technicians (public)
• GET /api/v1/technicians/:id - Get technician profile (public)
• GET /api/v1/technicians/:id/schedule - Get schedule
• PUT /api/v1/technicians/:id/availability - Update availability
• PUT /api/v1/technicians/:id/schedule - Update schedule
• GET /api/v1/technicians/:id/bookings - Get technician bookings

Security & Validation

• JWT-based authentication with role verification
• Comprehensive validation middleware using express-validator
• Input sanitization and type checking
• Authorization checks for resource access
• Error handling with consistent response format

📁 Files Added/Modified

New Files

• Controllers/BookingController.js - Complete booking management logic
• Controllers/TechnicianController.js - Enhanced technician operations
• routes/BookingRoutes.js - Booking API endpoints with auth
• routes/TechnicianRoutes.js - Technician API endpoints
• MiddleWare/ValidationMiddleware.js - Input validation rules
• API_DOCUMENTATION.md - Comprehensive API documentation
• test_api.sh - Testing script for endpoint verification

Modified Files

• prisma/schema.prisma - Added Booking and TechnicianAvailability models
• server.js - Integrated new routes
• Database migration for new models

🧪 Testing

The implementation includes:

• Mock Prisma client for testing without database connection
• Test script demonstrating all endpoints
• Validation testing for input sanitization
• Authentication testing for security verification

Example usage:

# Start server
npm start

# Test endpoints
./test_api.sh

# Test specific endpoint
curl -X GET "http://localhost:3000/api/v1/technicians?page=1&limit=5"

📋 Business Logic Coverage

✅ Booking creation, update, and management endpoints
✅ Booking status tracking
✅ Booking history and filtering
✅ Technician profile management
✅ Availability and scheduling APIs

The implementation provides a complete foundation for the TechCare booking system with:

• Scalable architecture following existing patterns
• Role-based security model
• Comprehensive validation and error handling
• Extensible design for future enhancements

Fixes #33.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• binaries.prisma.sh
  • Triggering command: node scripts/postinstall.js (dns block)
  • Triggering command: node /home/REDACTED/work/tech-care/tech-care/backend/node_modules/.bin/prisma -v (dns block)
  • Triggering command: node /home/REDACTED/work/tech-care/tech-care/backend/node_modules/.bin/prisma generate (dns block)
• checkpoint.prisma.io
  • Triggering command: /usr/local/bin/node /home/REDACTED/work/tech-care/tech-care/backend/node_modules/prisma/build/child {"product":"prisma","version":"6.11.1","cli_install_type":"local","information":"","local_timestamp":"2025-07-15T03:56:24Z","project_hash":"3c841e43","cli_path":"/home/REDACTED/work/tech-care/tech-care/backend/node_modules/.bin/prisma","cli_path_hash":"ba7350ea","endpoint":"REDACTED","disable":false,"arch":"x64","os":"linux","node_version":"v20.19.3","ci":true,"ci_name":"GitHub Actions","command":"generate","schema_providers":["postgresql"],"schema_preview_features":[],"schema_generators_providers":["prisma-client-js"],"cache_file":"/home/REDACTED/.cache/checkpoint-nodejs/prisma-ba7350ea","cache_duration":43200000,"remind_duration":172800000,"force":false,"timeout":5000,"unref":true,"child_path":"/home/REDACTED/work/tech-care/tech-care/backend/node_modules/prisma/build/child","client_event_id":"","previous_client_event_id":"","check_if_update_available":true} (dns block)
  • Triggering command: /usr/local/bin/node /home/REDACTED/work/tech-care/tech-care/backend/node_modules/prisma/build/child {"product":"prisma","version":"6.11.1","cli_install_type":"local","information":"","local_timestamp":"2025-07-15T04:00:37Z","project_hash":"3c841e43","cli_path":"/home/REDACTED/work/tech-care/tech-care/backend/node_modules/.bin/prisma","cli_path_hash":"ba7350ea","endpoint":"REDACTED","disable":false,"arch":"x64","os":"linux","node_version":"v20.19.3","ci":true,"ci_name":"GitHub Actions","command":"migrate dev --name [redacted] --create-only","schema_providers":["postgresql"],"schema_preview_features":[],"schema_generators_providers":["prisma-client-js"],"cache_file":"/home/REDACTED/.cache/checkpoint-nodejs/prisma-ba7350ea","cache_duration":43200000,"remind_duration":172800000,"force":false,"timeout":5000,"unref":true,"child_path":"/home/REDACTED/work/tech-care/tech-care/backend/node_modules/prisma/build/child","client_event_id":"","previous_client_event_id":"","check_if_update_available":true} (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.