feat(wren-ui): remove unnecessary sql column of thread table

[fredalai]

Description

The sql column in the thread table is no longer in use, so we will remove it.

Summary by CodeRabbit

• New Features

  • Streamlined thread data structure by removing the sql field from various types and operations.

• Bug Fixes

  • Adjusted GraphQL queries and mutations to ensure they no longer reference the deprecated sql field.

• Refactor

  • Updated methods in the AskingService to eliminate SQL handling during thread creation.

• Documentation

  • Enhanced clarity in thread representation by removing unnecessary SQL fields from the schema and types.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request involves the removal of the sql field from multiple components of the Wren UI application. Changes affect various files in the GraphQL schema, types, services, and a database migration script. The modifications indicate a shift away from SQL-related information in thread representations, aiming for a more streamlined data model for threads across both client and server-side implementations.

Changes

File	Change Summary
wren-ui/migrations/20241226135712_remove_thread_sql.js	Added migration script to drop sql column from thread table and update foreign key constraints.
wren-ui/src/apollo/client/graphql/__types__.ts	Removed sql field from DetailedThread and Thread types.
wren-ui/src/apollo/client/graphql/home.generated.ts	Removed sql field from ThreadQuery, CreateThreadMutation, and UpdateThreadMutation.
wren-ui/src/apollo/client/graphql/home.ts	Removed sql field from THREAD, CREATE_THREAD, and UPDATE_THREAD operations.
wren-ui/src/apollo/server/repositories/threadRepository.ts	Removed sql property from Thread interface.
wren-ui/src/apollo/server/schema.ts	Removed sql field from Thread and DetailedThread GraphQL types.
wren-ui/src/apollo/server/services/askingService.ts	Removed sql assignment in createThread and createThreadFromView methods.

Sequence Diagram

sequenceDiagram
    participant Client
    participant GraphQL
    participant Service
    participant Database
    
    Client->>GraphQL: Create Thread Request
    GraphQL->>Service: Process Thread Creation
    Service->>Database: Insert Thread
    Database-->>Service: Thread Created
    Service-->>GraphQL: Return Thread (without SQL)
    GraphQL-->>Client: Thread Response

Loading

Poem

🐰 A Rabbit's Migration Tale 🗃️
SQL, oh SQL, you've had your day,
From threads you're now swept away,
Migration's dance, a clean refrain,
No more queries to retain,
Hop-hop, farewell to bygone strain! 🚀

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ad569c1 and 0820cf2.

📒 Files selected for processing (7)

• wren-ui/migrations/20241226135712_remove_thread_sql.js (1 hunks)
• wren-ui/src/apollo/client/graphql/__types__.ts (0 hunks)
• wren-ui/src/apollo/client/graphql/home.generated.ts (3 hunks)
• wren-ui/src/apollo/client/graphql/home.ts (0 hunks)
• wren-ui/src/apollo/server/repositories/threadRepository.ts (0 hunks)
• wren-ui/src/apollo/server/schema.ts (0 hunks)
• wren-ui/src/apollo/server/services/askingService.ts (0 hunks)

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[wwwy3y3]

others LGTM