💥 Migrate to snake_case table/column name in frontend/apps/app

.ai-agents/memory-bank/activeContext.md

@@ -18,35 +18,35 @@ The current focus is on enhancing the Reviewer User experience with AI-driven an
    - Updated package.json to replace @langchain/anthropic with @langchain/openai v0.5.5
    - This change standardizes the AI model usage across the application and potentially improves performance and cost-efficiency
 
-2. **Added Reasoning Field to KnowledgeSuggestion**: Enhanced the KnowledgeSuggestion table to store the rationale behind schema override update suggestions:
+2. **Added Reasoning Field to knowledge_suggestions**: Enhanced the knowledge_suggestions table to store the rationale behind schema override update suggestions:
    - Created a migration to add a `reasoning` TEXT field with a default empty string value
    - Updated the database.types.ts file to include the new field in the type definitions
    - Modified the KnowledgeSuggestionDetailPage.tsx component to display the reasoning field when available
    - This enhancement helps users understand the context and rationale behind schema override update suggestions, enabling more informed decisions when approving suggestions
 
-2. **OverallReview to KnowledgeSuggestion Relationship**: Implemented a relationship between OverallReview and KnowledgeSuggestion tables:
-   - Created a new intermediate table `OverallReviewKnowledgeSuggestionMapping` to link OverallReview and KnowledgeSuggestion
-   - Modified `processCreateKnowledgeSuggestion.ts` to accept an optional `overallReviewId` parameter
-   - Implemented `createOverallReviewMapping` function to create mappings in the OverallReviewKnowledgeSuggestionMapping table
-   - Enhanced the MigrationDetailPage to fetch and display related KnowledgeSuggestions
-   - Updated UI to show KnowledgeSuggestions in a dedicated section on the MigrationDetailPage
+2. **overall_reviews to knowledge_suggestions Relationship**: Implemented a relationship between overall_reviews and knowledge_suggestions tables:
+   - Created a new intermediate table `overall_review_knowledge_suggestion_mappings` to link overall_reviews and knowledge_suggestions
+   - Modified `processCreateKnowledgeSuggestion.ts` to accept an optional `overall_review_id` parameter
+   - Implemented `createOverallReviewMapping` function to create mappings in the overall_review_knowledge_suggestion_mappings table
+   - Enhanced the MigrationDetailPage to fetch and display related knowledge_suggestions
+   - Updated UI to show knowledge_suggestions in a dedicated section on the MigrationDetailPage
    - Implemented proper navigation using the urlgen utility for type-safe route generation
-   - This allows users to track and navigate to KnowledgeSuggestions from the MigrationDetailPage
+   - This allows users to track and navigate to knowledge_suggestions from the MigrationDetailPage
 
-2. **Optimized KnowledgeSuggestion Creation**: Enhanced the `processCreateKnowledgeSuggestion.ts` function to avoid creating unnecessary suggestions:
+2. **Optimized knowledge_suggestion Creation**: Enhanced the `processCreateKnowledgeSuggestion.ts` function to avoid creating unnecessary suggestions:
    - Implemented content comparison to check if document content has changed before creating a suggestion
    - Refactored the function into smaller, focused helper functions to reduce cognitive complexity
    - Improved type safety with proper type definitions and return types
-   - Optimized database queries by caching the GitHubDocFilePath query result
+   - Optimized database queries by caching the github_doc_file_paths query result
    - Enhanced error handling with more specific error messages
    - This optimization prevents duplicate suggestions when content hasn't changed
 
-2. **KnowledgeSuggestion and GitHubDocFilePath Integration**: Implemented a connection between KnowledgeSuggestion and GitHubDocFilePath tables:
-   - Created a new intermediate table `KnowledgeSuggestionDocMapping` to link KnowledgeSuggestion and GitHubDocFilePath
+2. **knowledge_suggestions and github_doc_file_paths Integration**: Implemented a connection between knowledge_suggestions and github_doc_file_paths tables:
+   - Created a new intermediate table `knowledge_suggestion_doc_mappings` to link knowledge_suggestions and github_doc_file_paths
    - Modified `processCreateKnowledgeSuggestion.ts` to create mappings for existing docs when creating a Doc Suggestion
-   - Updated `approveKnowledgeSuggestion.ts` to create GitHubDocFilePath entries and mappings for new docs
+   - Updated `approveKnowledgeSuggestion.ts` to create github_doc_file_paths entries and mappings for new docs
    - Refactored code to reduce cognitive complexity and improve type safety
-   - This ensures that newly created Knowledge suggestions are properly included in reviews
+   - This ensures that newly created knowledge suggestions are properly included in reviews
 
 3. **Database Migration Documentation**: Created comprehensive documentation for the Supabase migration workflow:
    - Added detailed migration guidelines in `docs/migrationOpsContext.md`
@@ -80,7 +80,7 @@ The current focus is on enhancing the Reviewer User experience with AI-driven an
 
 7. **Database Schema Optimization**:
    - Removed unused Doc and DocVersion models
-   - Renamed `WatchSchemaFilePattern` table to `GitHubSchemaFilePath`
+   - Renamed `watch_schema_file_patterns` table to `github_schema_file_paths`
    - Changed from pattern matching to direct path comparison for schema file management
 
 8. **Supabase JS Integration**:
@@ -137,7 +137,7 @@ The current focus is on enhancing the Reviewer User experience with AI-driven an
 4. **Schema File Management**:
    - Using direct path comparison instead of pattern matching
    - Providing more precise and efficient approach
-   - Aligning with existing GitHubDocFilePath model
+   - Aligning with existing github_doc_file_paths model
 
 5. **Function Organization**:
    - Breaking down complex functions into smaller, focused helper functions

.ai-agents/memory-bank/progress.md

@@ -7,9 +7,9 @@
 - The GitHub App integration is operational, automating comments and review approvals on PRs.
 - Complete review pipeline from GitHub webhook to AI review generation to PR comment posting.
 - Modular architecture with separate functions for review generation and comment posting.
-- KnowledgeSuggestion database model for storing and managing AI-generated suggestions for Schema and Docs updates, now with a reasoning field to provide context and rationale for suggestions.
+- knowledge_suggestions database model for storing and managing AI-generated suggestions for Schema and Docs updates, now with a reasoning field to provide context and rationale for suggestions.
 - Text document viewer page that renders raw text content from GitHub repositories.
-- Documentation list page that displays all GitHubDocFilePath entries for a project with links to individual document pages.
+- Documentation list page that displays all github_doc_file_paths entries for a project with links to individual document pages.
 - Supabase JS integration for database access in multiple components, including:
   - Document viewer page with optimized queries using nested joins
   - ProjectBranchesListPage component for listing project branches
@@ -20,19 +20,19 @@
 - Schema override generation pipeline that creates and stores schema override suggestions based on PR reviews, with context-aware prompts that include both existing schema override and actual schema files content for more accurate suggestions.
 - Reusable utility function for fetching schema files content that can be used across different components of the application.
 - Type-safe implementation of Supabase queries with proper handling of bigint fields and nested relationships.
-- Improved schema file management with the GitHubSchemaFilePath table (renamed from WatchSchemaFilePattern) and direct path comparison instead of pattern matching.
+- Improved schema file management with the github_schema_file_paths table (renamed from watch_schema_file_patterns) and direct path comparison instead of pattern matching.
 - Standardized Supabase client usage across the codebase using a shared createClient function.
 - Enhanced review generation with PR context, incorporating pull request descriptions and comments for more comprehensive analysis.
 - Improved naming consistency throughout the codebase, with `fileChanges` replacing `schemaChanges` for better clarity.
 - Standardized Supabase database migration workflow documented.
-- Implemented KnowledgeSuggestionDocMapping table to link KnowledgeSuggestion and GitHubDocFilePath tables, ensuring newly created Knowledge suggestions are properly included in reviews.
+- Implemented knowledge_suggestion_doc_mappings table to link knowledge_suggestions and github_doc_file_paths tables, ensuring newly created knowledge suggestions are properly included in reviews.
 - Enhanced processCreateKnowledgeSuggestion.ts to create mappings for existing docs when creating a Doc Suggestion.
-- Updated approveKnowledgeSuggestion.ts to create GitHubDocFilePath entries and mappings for new docs when approving a Doc Suggestion.
-- Optimized KnowledgeSuggestion creation to avoid duplicate suggestions by checking if content has changed before creating a new suggestion.
+- Updated approveKnowledgeSuggestion.ts to create github_doc_file_paths entries and mappings for new docs when approving a Doc Suggestion.
+- Optimized knowledge_suggestion creation to avoid duplicate suggestions by checking if content has changed before creating a new suggestion.
 - Refactored complex functions into smaller, focused helper functions to reduce cognitive complexity and improve maintainability.
 - Improved type safety with proper type definitions and return types for functions.
-- Implemented relationship between OverallReview and KnowledgeSuggestion tables using an intermediate mapping table (OverallReviewKnowledgeSuggestionMapping), allowing users to track and navigate to KnowledgeSuggestions from the MigrationDetailPage.
-- Enhanced MigrationDetailPage to fetch and display related KnowledgeSuggestions with proper navigation using the urlgen utility for type-safe route generation.
+- Implemented relationship between overall_reviews and knowledge_suggestions tables using an intermediate mapping table (overall_review_knowledge_suggestion_mappings), allowing users to track and navigate to knowledge_suggestions from the MigrationDetailPage.
+- Enhanced MigrationDetailPage to fetch and display related knowledge_suggestions with proper navigation using the urlgen utility for type-safe route generation.
 
 ## What's Left to Build
 
@@ -51,7 +51,7 @@ Several key components are now using Supabase for database access, including the
 
 The core review pipeline is now operational, connecting GitHub webhooks to AI-powered review generation and PR comment posting. This enables automatic review of database schema changes when pull requests are opened or updated.
 
-The KnowledgeSuggestion feature has been enhanced to be more efficient and maintainable. Recent improvements include:
+The knowledge_suggestions feature has been enhanced to be more efficient and maintainable. Recent improvements include:
 
 1. Optimizing the creation process to check if content has changed before creating a new suggestion, preventing duplicate suggestions
 2. Refactoring complex functions into smaller, focused helper functions to reduce cognitive complexity
@@ -63,17 +63,17 @@ These improvements align with the project's focus on code quality, maintainabili
 
 A new text document viewer page has been implemented at `/app/projects/[projectId]/docs/[branchOrCommit]/[...slug]` that fetches and displays raw text content from GitHub repositories. The implementation uses a single optimized Supabase query with nested joins to efficiently retrieve all necessary data.
 
-A documentation list page has been implemented at `/app/projects/[projectId]/ref/[branchOrCommit]/docs` that displays all GitHubDocFilePath entries for a project. The page provides links to individual document pages and shows the review status of each document. This enhances the user experience by providing a centralized view of all documentation files associated with a project.
+A documentation list page has been implemented at `/app/projects/[projectId]/ref/[branchOrCommit]/docs` that displays all github_doc_file_paths entries for a project. The page provides links to individual document pages and shows the review status of each document. This enhances the user experience by providing a centralized view of all documentation files associated with a project.
 
-The database schema has been optimized by removing the unused Doc and DocVersion models. Document management is now fully handled through the GitHubDocFilePath model, which provides a more direct integration with GitHub repositories. This change reflects the project's shift towards tighter GitHub integration and a more streamlined approach to document handling.
+The database schema has been optimized by removing the unused Doc and DocVersion models. Document management is now fully handled through the github_doc_file_paths model, which provides a more direct integration with GitHub repositories. This change reflects the project's shift towards tighter GitHub integration and a more streamlined approach to document handling.
 
-A new schema override generation pipeline has been implemented that creates and stores schema override suggestions based on PR reviews. This pipeline includes a new task (`generateSchemaOverrideSuggestionTask`) that is triggered after a review is saved, a processing function (`processGenerateSchemaOverride`) that fetches data from the database and generates schema override suggestions, and integration with the existing `createKnowledgeSuggestionTask` to store the generated schema override. The implementation includes proper type handling for Supabase queries, addressing challenges with bigint fields and nested relationships. Recent enhancements include fetching and passing both the current schema override and actual schema files content to the AI prompt, allowing for more informed and contextually relevant suggestions that build upon existing schema override rather than generating from scratch. A reusable utility function has been created to fetch schema files content, which can be used in other parts of the application. The implementation also includes type-safe validation of the existing schema override using Valibot's `safeParse` function.
+A new schema override generation pipeline has been implemented that creates and stores schema override suggestions based on PR reviews. This pipeline includes a new task (`generateSchemaOverrideSuggestionTask`) that is triggered after a review is saved, a processing function (`processGenerateSchemaOverride`) that fetches data from the database and generates schema override suggestions, and integration with the existing `createKnowledgeSuggestionTask` to store the generated schema override in the knowledge_suggestions table. The implementation includes proper type handling for Supabase queries, addressing challenges with bigint fields and nested relationships. Recent enhancements include fetching and passing both the current schema override and actual schema files content to the AI prompt, allowing for more informed and contextually relevant suggestions that build upon existing schema override rather than generating from scratch. A reusable utility function has been created to fetch schema files content, which can be used in other parts of the application. The implementation also includes type-safe validation of the existing schema override using Valibot's `safeParse` function.
 
 As part of the transition to Supabase JS, manual rollback processing has been removed from the `addProject.ts` server action. This change prepares the way for implementing more robust transaction management using Supabase RPC in the future, which will provide a more consistent approach to handling database transactions across the application.
 
 The testing approach uses a direct testing strategy with Supabase. We create real records in the database, run the actual functions with these records, and then clean up the test data afterwards. This approach provides more realistic tests that verify the actual functions with real database interactions, leveraging Supabase's ability to be executed directly in test environments.
 
-The schema file management has been improved by renaming the `WatchSchemaFilePattern` table to `GitHubSchemaFilePath` and changing from pattern matching to direct path comparison. This provides a more precise and efficient approach to schema file management, aligning with the existing `GitHubDocFilePath` model and providing a more consistent approach to file path handling across the application. The implementation includes a migration file that handles the table rename and data transfer, updates to all affected components to use the new table name and field names, and standardization of Supabase client usage across the codebase.
+The schema file management has been improved by renaming the `watch_schema_file_patterns` table to `github_schema_file_paths` and changing from pattern matching to direct path comparison. This provides a more precise and efficient approach to schema file management, aligning with the existing `github_doc_file_paths` model and providing a more consistent approach to file path handling across the application. The implementation includes a migration file that handles the table rename and data transfer, updates to all affected components to use the new table name and field names, and standardization of Supabase client usage across the codebase.
 
 A standardized Supabase migration workflow has been documented in `docs/migrationOpsContext.md`. This document provides detailed guidance on the migration workflow, deployment system, key constraints, and SQL guidelines for creating migrations. Additionally, the `docs/schemaPatterns.md` document defines reusable patterns and rules for database schema design, ensuring consistency across the project. The Supabase migration workflow uses commands like `supabase:migration:new` and `supabase:migration:up` to manage database schema changes.