mirror of https://github.com/SamyRai/turash.git synced 2025-12-26 23:01:33 +00:00

Consolidate repositories: Remove nested frontend .git and merge into main repository

- Remove nested git repository from bugulma/frontend/.git
- Add all frontend files to main repository tracking
- Convert from separate frontend/backend repos to unified monorepo
- Preserve all frontend code and development history as tracked files
- Eliminate nested repository complexity for simpler development workflow

This creates a proper monorepo structure with frontend and backend
coexisting in the same repository for easier development and deployment.

2025-11-25 06:02:57 +01:00

1.8 KiB

Raw Blame History

Legacy Code Cleanup

This document tracks the removal of legacy frontend-only code that has been moved to the backend.

✅ Deleted Files

LLM/AI Direct Calls

❌ services/geminiService.ts - Replaced by services/aiService.ts (calls backend)
❌ lib/llm/ (entire directory) - No longer needed, backend handles LLM

Business Logic

❌ lib/analytics.ts - Analytics now come from backend API
❌ lib/analytics.test.ts - Tests for removed analytics functions
❌ lib/organizationUtils.ts - Similar organizations now from backend API
❌ lib/organizationUtils.test.ts - Tests for removed utility

Static Data

❌ data/proposals.ts - Proposals now come from backend API

📝 Files Still Present (Documentation Only)

These files are kept for reference but are no longer used in code:

LLM_ABSTRACTION.md - Documentation of the LLM abstraction (for backend reference)
FRONTEND_SIMPLIFICATION.md - Documentation of the simplification
BACKEND_MIGRATION_REVIEW.md - Review document

🔄 Migration Summary

Before (Frontend-Only)

Direct LLM API calls with API keys in frontend
Business logic in frontend (matching, analytics, filtering)
Static data files
Client-side calculations

After (Backend-Driven)

All AI/LLM calls go through backend API
All business logic on backend
All data from backend API
Frontend is "dumb" - just displays data and calls APIs

Remaining Frontend Logic

The following frontend logic is acceptable to keep:

✅ UI state management (tabs, modals, form state)
✅ Client-side filtering for UX (debouncing, instant feedback)
✅ Client-side sorting for small datasets
✅ Component composition and rendering
✅ Routing and navigation
✅ Theme and localization

All business logic, calculations, and data persistence are now handled by the backend.

1.8 KiB Raw Blame History