How mithila-minidul/travel-planning-itinerary-platform works
This is a full-stack travel-planning platform: travelers and travel professionals browse experiences, organize trips, book and pay, then manage reviews; a Python agent workflow can generate itinerary suggestions that the .NET backend persists. The React application provides role-gated views, while the backend exposes domain APIs and PostgreSQL-backed services. The README identifies the platform and agentic-AI scope, but offers few workflow details; several links below rely on indexed imports or registrations, and unsampled integrations are omitted or marked unverified.
Main entry points: Program.cs HTTP API · App.jsx Web routes · AppDbContext.cs EF data context · PlannerAgentService.cs Itinerary bridge
Components 26
Web application
- Web routes
frontend/src/App.jsx - Session context
frontend/src/context/AuthContext.jsx - Trip views
frontend/src/pages/TripsPage.jsx - Review views
frontend/src/pages/ReviewManagementPage.jsx - API client
frontend/src/api/client.js
Platform backend
- HTTP API
backend/Program.cs - Trip endpoints
backend/Controllers/TripsController.cs - Booking endpoints
backend/Controllers/BookingsController.cs - Review endpoints
backend/Controllers/ReviewsController.cs - Itinerary bridge
backend/Services/PlannerAgentService.cs - Booking services
backend/Services/BookingService.cs - Review services
backend/Services/ReviewService.cs - Travel catalog
backend/Services/Member1Services.cs - Payment services
backend/Services/PaymentService.cs
AI itinerary planning
- Itinerary workflow
ai-service/workflows/trip_planner_workflow.py - Planning agents
ai-service/agents - Research agent
ai-service/agents/research_agent.py - AI service routes
ai-service/main.py
Travel data
- PostgreSQL
- Travel entities
backend/Models/Trip.cs - EF data context
backend/Data/AppDbContext.cs
Other components
- Traveler
- Local guide
- Administrator
- PayHere gateway
- LLM provider
Connections 28
- Traveler → Web routes: uses
frontend/src/App.jsx - Local guide → Web routes: uses
frontend/src/App.jsx - Administrator → Web routes: uses
frontend/src/App.jsx - Web routes → Session context: provides session
frontend/src/App.jsx - Web routes → Trip views: routes to
frontend/src/App.jsx - Web routes → Review views: routes to
frontend/src/App.jsx - Session context → API client: uses auth API
frontend/src/context/AuthContext.jsx - Review views → API client: loads reviews
frontend/src/pages/ReviewManagementPage.jsx - API client → HTTP API: HTTP requests
- HTTP API → Trip endpoints: maps controllers
backend/Program.cs - HTTP API → Booking endpoints: maps controllers
backend/Program.cs - HTTP API → Review endpoints: maps controllers
backend/Program.cs - Trip endpoints → Itinerary bridge: requests itinerary
- Booking endpoints → Booking services: delegates booking
backend/Controllers/BookingsController.cs - Review endpoints → Review services: delegates reviews
backend/Controllers/ReviewsController.cs - HTTP API → Travel catalog: registers services
backend/Program.cs - HTTP API → Payment services: registers services
backend/Program.cs - Itinerary bridge → AI service routes: posts itinerary request
backend/Services/PlannerAgentService.cs - AI service routes → Itinerary workflow: dispatches workflow
ai-service/main.py - AI service routes → Planning agents: loads agents
ai-service/main.py - Planning agents → Research agent: includes research
- Research agent → LLM provider: uses client
- Itinerary bridge → EF data context: maps itinerary stops
backend/Services/PlannerAgentService.cs - EF data context → PostgreSQL: reads and writes
- EF data context → Travel entities: maps entities
backend/Data/AppDbContext.cs - Review services → EF data context: queries and saves
backend/Services/ReviewService.cs - Booking services → EF data context: uses persistence
- Payment services → PayHere gateway: gateway integration