Connect routing logic with user preferences (requires authentication)

[Copilot]

Enable AI-generated route insights to incorporate user preferences from both request payload and stored user settings. The /routes/search endpoint now requires authentication.

Changes

Schema

• Added optional preferences: List[str] field to RouteSearchRequest

Endpoint (/routes/search)

• Requires authentication - only authenticated users can access the endpoint
• Collect preferences from two sources:
  1. Request body (explicit preferences)
  2. Stored user preferences (from authenticated user)
• Pass combined list to AI service with graceful degradation on preference fetch failure

AI Service

• Updated get_itinerary_insight(itinerary, user_preferences=None) to accept optional preferences
• Include user_preferences in payload to /api/v1/insight/itinerary when provided

Example Usage

# Authenticated request with explicit preferences
POST /api/v1/routes/search
Authorization: Bearer <token>
{
  "origin": {"latitude": 60.17, "longitude": 24.94},
  "destination": {"latitude": 60.21, "longitude": 24.66},
  "preferences": ["prefer walking", "avoid crowded buses"]
}

# Authenticated request - merges stored preferences with request preferences
POST /api/v1/routes/search
Authorization: Bearer <token>
{
  "origin": {...},
  "destination": {...},
  "preferences": ["prefer trams"]  # Combined with stored: ["avoid buses", "eco-friendly"]
}

AI agents receive:

{
  "duration": 2700,
  "legs": [...],
  "user_preferences": ["prefer trams", "avoid buses", "eco-friendly"]
}

Note: Unauthenticated requests will receive a 401 Unauthorized response.

• Fixes Connect the routing logic with the preferences #36

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Connect the routing logic with the preferences</issue_title>
<issue_description>- search endpoint sends user preferences to AI service

• Returning object from get_itinerary_insight stays the same
• Insight enhancement business logic handled by backend
  • Interface change with insight/itinerary is that it can now take in user preferences
• Write tests to cover new feature</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Connect the routing logic with the preferences #36

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[zlendo1]

@copilot Make sure that search endpoint can only be reached by an existing current user (disallow unauthorized access).

[Copilot]

@copilot Make sure that search endpoint can only be reached by an existing current user (disallow unauthorized access).

Updated the /routes/search endpoint to require authentication. The endpoint now uses get_current_user instead of the optional authentication, so unauthorized access is disallowed.

All tests have been updated to provide authentication and all 91 tests pass successfully.

Commit: 10936c5