kincses/service-finder
1
0
Fork 0
Code Issues 33 Pull Requests Packages Projects 2 Releases Wiki Activity

Implement Catalog API Endpoints #142

New Issue
Open
opened 2026-03-26 09:09:05 +01:00 by kincses · 0 comments
kincses commented 2026-03-26 09:09:05 +01:00
Owner
Copy Link

Objective: Implement catalog API endpoints (, ) that currently return 404, causing empty dropdowns in vehicle selection UI.

Target Files:

  • Backend: Create
  • Models: Connect to table
  • Schemas: Create

Acceptance Criteria:

  1. GET returns list of unique vehicle brands
  2. GET returns filtered models by brand, year, fuel type
  3. API responses match frontend expected format (check existing frontend components)
  4. No mock data - must query real table

Execution Steps:

  1. Create catalog endpoint module with proper FastAPI router
  2. Implement SQL queries to get distinct brands and filtered models
  3. Add filtering parameters (brand, year_range, fuel_type)
  4. Test endpoints with Postman/curl
  5. Verify frontend dropdowns populate with real data

Technical Details:

  • Estimated effort: 2 days
  • Dependencies: Task 1.1 (vehicle creation fix)
  • Priority: P0 (blocks vehicle selection)
**Objective:** Implement catalog API endpoints (, ) that currently return 404, causing empty dropdowns in vehicle selection UI. **Target Files:** - Backend: Create - Models: Connect to table - Schemas: Create **Acceptance Criteria:** 1. GET returns list of unique vehicle brands 2. GET returns filtered models by brand, year, fuel type 3. API responses match frontend expected format (check existing frontend components) 4. No mock data - must query real table **Execution Steps:** 1. Create catalog endpoint module with proper FastAPI router 2. Implement SQL queries to get distinct brands and filtered models 3. Add filtering parameters (brand, year_range, fuel_type) 4. Test endpoints with Postman/curl 5. Verify frontend dropdowns populate with real data **Technical Details:** - Estimated effort: 2 days - Dependencies: Task 1.1 (vehicle creation fix) - Priority: P0 (blocks vehicle selection)
kincses added this to the Phase 1: Core Functionality Fixes milestone 2026-03-26 09:09:05 +01:00
kincses added the Status: To DoScope: BackendType: Feature labels 2026-03-26 09:09:06 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Role: Admin
👑 Role: Admin
 Role: User
👤 Role: User
 Scope: API
🔌 Scope: API
 Scope: Backend
🏗️ Scope: Backend
 Scope: Core
⚙️ Scope: Core
 Scope: Database
Scope: Frontend
🖥️ Scope: Frontend
 Scope: Robot
Status: Blocked
Status: Done
Status: In Progress
Status: To Do
Type: Bug
🐞 Type: Bug
 Type: Database
💾 Type: Database
 Type: Feature
✨ Type: Feature
 Type: Model
🧠 Type: Model
 Type: Refactor
Type: Refactor
Type: Script
📜 Type: Script
No Label Scope: Backend Status: To Do Type: Feature
Milestone
No items
No Milestone Phase 1: Core Functionality Fixes
Projects
Clear projects
No project
Assignees
Clear assignees
kincses
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kincses/service-finder#142
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?