AI Analysis and Content Strategy fixes. Enhanced Strategy Routes refactoring.
This commit is contained in:
64
backend/api/content_planning/docs/ROUTE_FIX_SUMMARY.md
Normal file
64
backend/api/content_planning/docs/ROUTE_FIX_SUMMARY.md
Normal file
@@ -0,0 +1,64 @@
|
||||
# Route Fix Summary - Enhanced Strategies Endpoints
|
||||
|
||||
## Issue
|
||||
After refactoring, frontend was getting 404 errors for:
|
||||
- `GET /api/content-planning/enhanced-strategies`
|
||||
- `GET /api/content-planning/enhanced-strategies/stream/strategic-intelligence`
|
||||
|
||||
## Root Cause
|
||||
The router prefix was changed from `/enhanced-strategies` to `/content-strategy` during refactoring, breaking backward compatibility with frontend API calls.
|
||||
|
||||
## Solution Applied
|
||||
Updated `content_strategy/routes.py` to use `/enhanced-strategies` prefix for backward compatibility:
|
||||
|
||||
```python
|
||||
router = APIRouter(prefix="/enhanced-strategies", tags=["Content Strategy"])
|
||||
```
|
||||
|
||||
## Current Route Structure
|
||||
|
||||
### Main Router
|
||||
- Base: `/api/content-planning`
|
||||
- Content Strategy Router: `/enhanced-strategies`
|
||||
|
||||
### Endpoint Paths
|
||||
- **CRUD Endpoints** (prefix: `""`):
|
||||
- `GET /api/content-planning/enhanced-strategies/` → `strategy_crud.py` `GET /`
|
||||
- `POST /api/content-planning/enhanced-strategies/create` → `strategy_crud.py` `POST /create`
|
||||
- `GET /api/content-planning/enhanced-strategies/{strategy_id}` → `strategy_crud.py` `GET /{strategy_id}`
|
||||
- `PUT /api/content-planning/enhanced-strategies/{strategy_id}` → `strategy_crud.py` `PUT /{strategy_id}`
|
||||
- `DELETE /api/content-planning/enhanced-strategies/{strategy_id}` → `strategy_crud.py` `DELETE /{strategy_id}`
|
||||
|
||||
- **Streaming Endpoints** (prefix: `""`):
|
||||
- `GET /api/content-planning/enhanced-strategies/stream/strategies` → `streaming_endpoints.py`
|
||||
- `GET /api/content-planning/enhanced-strategies/stream/strategic-intelligence` → `streaming_endpoints.py`
|
||||
- `GET /api/content-planning/enhanced-strategies/stream/keyword-research` → `streaming_endpoints.py`
|
||||
|
||||
- **Utility Endpoints** (prefix: `""`):
|
||||
- `GET /api/content-planning/enhanced-strategies/onboarding-data` → `utility_endpoints.py`
|
||||
- `GET /api/content-planning/enhanced-strategies/tooltips` → `utility_endpoints.py`
|
||||
- `GET /api/content-planning/enhanced-strategies/disclosure-steps` → `utility_endpoints.py`
|
||||
- `POST /api/content-planning/enhanced-strategies/cache/clear` → `utility_endpoints.py`
|
||||
|
||||
- **Analytics Endpoints** (prefix: `/strategies`):
|
||||
- `GET /api/content-planning/enhanced-strategies/strategies/{strategy_id}/analytics` → `analytics_endpoints.py`
|
||||
- `GET /api/content-planning/enhanced-strategies/strategies/{strategy_id}/ai-analyses` → `analytics_endpoints.py`
|
||||
- `GET /api/content-planning/enhanced-strategies/strategies/{strategy_id}/completion` → `analytics_endpoints.py`
|
||||
- `GET /api/content-planning/enhanced-strategies/strategies/{strategy_id}/onboarding-integration` → `analytics_endpoints.py`
|
||||
- `POST /api/content-planning/enhanced-strategies/strategies/{strategy_id}/ai-recommendations` → `analytics_endpoints.py`
|
||||
- `POST /api/content-planning/enhanced-strategies/strategies/{strategy_id}/ai-analysis/regenerate` → `analytics_endpoints.py`
|
||||
|
||||
- **Autofill Endpoints** (prefix: `/strategies`):
|
||||
- `POST /api/content-planning/enhanced-strategies/strategies/{strategy_id}/autofill/accept` → `autofill_endpoints.py`
|
||||
- `GET /api/content-planning/enhanced-strategies/autofill/refresh/stream` → `autofill_endpoints.py`
|
||||
- `POST /api/content-planning/enhanced-strategies/autofill/refresh` → `autofill_endpoints.py`
|
||||
|
||||
## Status
|
||||
✅ Routes should now match frontend expectations
|
||||
✅ Backward compatibility maintained
|
||||
✅ All endpoints properly modularized
|
||||
|
||||
## Next Steps
|
||||
1. Restart backend server to ensure routes are registered
|
||||
2. Test frontend calls to verify 404 errors are resolved
|
||||
3. Monitor logs for any route conflicts
|
||||
Reference in New Issue
Block a user