refactor(home): Extract home page logic to useHome hook

[SyedaAnshrahGillani]

This pull request refactors the Home component to improve its structure and readability. The logic for handling suggested questions, creating threads, and managing the UI state has been extracted into a new custom hook called useHome.

This change simplifies the Home component and makes the code more reusable. The Home component is now much cleaner and easier to understand, and the logic for handling suggested questions and creating threads can be reused in other parts of the application.

Summary by CodeRabbit

• New Features

  • Introduced improved handling of suggested questions, thread creation, and settings on the home page for a more streamlined user experience.

• Refactor

  • Simplified the Home page's internal logic by consolidating multiple data fetching and event handling mechanisms into a single, reusable hook, resulting in cleaner and more maintainable code.

[coderabbitai[bot]]

Walkthrough

A new custom React hook, useHome, was introduced to encapsulate all home page logic, including data fetching, mutations, event handlers, and state management. The Home component was refactored to use this hook, removing direct usage of hooks and queries in the component itself. No changes were made to exported component signatures.

Changes

Cohort / File(s)	Change Summary
New Custom Hook wren-ui/src/hooks/useHome.ts	Introduced the useHome hook to manage home page logic: suggested questions, thread creation, settings, routing, and event handlers, using Apollo GraphQL and Next.js.
Home Page Refactor wren-ui/src/pages/home/index.tsx	Refactored the Home component to use the new useHome hook, removing all inline hooks, queries, and handlers. JSX and exports unchanged.

Sequence Diagram(s)

sequenceDiagram
    participant HomeComponent
    participant useHome
    participant ApolloGraphQL
    participant NextRouter

    HomeComponent->>useHome: Invoke useHome()
    useHome->>ApolloGraphQL: Fetch suggested questions, settings
    useHome->>ApolloGraphQL: Prepare createThread mutation
    useHome->>NextRouter: Setup routing handlers

    HomeComponent->>useHome: User selects suggested question
    useHome->>HomeComponent: Trigger prompt submission

    HomeComponent->>useHome: User creates new thread
    useHome->>ApolloGraphQL: Execute createThread mutation
    useHome->>ApolloGraphQL: Preload thread data
    useHome->>NextRouter: Navigate to new thread page

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

In burrows deep, new hooks arise,
To fetch and guide with clever ties.
The home page now is neat and bright,
Its logic tucked away from sight.
With queries, threads, and prompts in tow,
This rabbit’s work will smoothly flow! 🐇✨

[!NOTE]

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 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 64419769f4ad82852f95f558a37266cf378b92f0 and e120c20bba95eafb5f7bce6625a052a283102a39.

📒 Files selected for processing (2)

• wren-ui/src/hooks/useHome.ts (1 hunks)
• wren-ui/src/pages/home/index.tsx (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (2)

• wren-ui/src/hooks/useHome.ts
• wren-ui/src/pages/home/index.tsx

✨ Finishing Touches

• [ ] 📝 Generate Docstrings

🧪 Generate unit tests

• [ ] Create PR with unit tests
• [ ] Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @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.