Repository navigation
v0.2.0
Introducing the second development version of our project. In this version, we implemented some APIs:
- GET
/trips/search: Search and return the information of trips based on origin and destination, date. - GET
/trips/{:tripId}: Get the detail info of any trip based on the tripId - (Admin only)
GET/POST/PUT /trips: For admin page only, get all the trips or create new trip or update any trip - (Admin only)
GET /trips/admin/{:tripId}: For admin page only, get the detailed info of any trip (this API is changed to not be conflict with the similarAPI /trips/{:tripId} - (Admin only)
GET /trips/available-buses: For admin page only, get the available buses for a specific time slot - (Admin only)
GET /trips/bus/{:busId}/schedule: For admin page only, get bus schedule for a specific date range - (Admin only)
GET /trips/route/{:routeId}/schedule: For admin page only, get route schedule for a specific date range - (Admin only)
GET /trips/check-availability/{:busId}: For admin page only, check if a bus is available for a specific time slot - (Admin only)
POST /trips/assign-bus: For admin page only, assign a bus to a route with conflict checking - (Admin only)
GET /trips/conflicts/{:busId}: For admin page only, get conflicting trips for a specific bus and time slot