Revert "refactor(hooks): move hooks to root directory"

[Sma1lboy]

Reverts #132

Summary by CodeRabbit

• Refactor

  • Standardized the integration of contextual state and dependency management for chat and authentication-related features.
  • Improved code organization to facilitate maintenance and support future enhancements while ensuring a consistent user experience.

• Chore

  • Reorganized internal module paths and updated naming conventions across various components.
  • Enhanced code clarity, simplified dependency resolution, and laid the groundwork for improved stability and ongoing development.

[coderabbitai]

Walkthrough

This pull request updates several frontend components by standardizing import paths and adjusting naming conventions. Changes include adding new imports for context and mutation functionality (e.g., useContext, useMutation, ProjectContext) and updating hook and provider paths to reflect a reorganized directory structure. Minor renames (such as PascalCase for modal components and casing corrections for layout components) further improve clarity and maintainability without altering component logic.

Changes

File(s)	Change Summary
frontend/src/app/(main)/chat/Home.tsx	Added useContext, useMutation, and ProjectContext imports; updated hook import paths (e.g., useModels, useChatList, useChatStream) to simpler relative paths.
frontend/src/app/(main)/chat/MainLayout.tsx, frontend/src/app/hooks/useModels.ts, frontend/src/components/SignInModal.tsx, frontend/src/components/chat/chat-bottombar.tsx, frontend/src/components/chat/chat-list.tsx, frontend/src/components/chat/chat-topbar.tsx, frontend/src/components/code-engine/project-context.tsx, frontend/src/components/ui/sidebar.tsx, frontend/src/components/user-settings.tsx	Updated import paths for hooks and providers (e.g., useAuthContext, useAuth, useSpeechToText, etc.) to conform to the new directory structure.
frontend/src/app/(main)/chat/layout.tsx, frontend/src/app/(main)/page.tsx, frontend/src/app/layout.tsx	Modified layout and modal component import paths; updated naming conventions (e.g., PascalCase for modal components and file casing for MainLayout); added type imports from next.

Suggested reviewers

• ZHallen122
• PengyuChen01

Poem

I'm a nimble rabbit, hopping through the code,
Adjusting paths and names on this winding road.
With context and mutations, my hops feel light,
Bringing clarity to our code in flight.
Carrots of change inspire each line I write –
Code paths now sparkle, shining ever bright!

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

frontend/src/app/(main)/chat/MainLayout.tsx

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the config "next/core-web-vitals" to extend from. Please check that the name of the config is correct.

The config "next/core-web-vitals" was referenced from the config file in "/frontend/.eslintrc.json".

If you still have problems, please stop by https://eslint.org/chat/help to chat with the team.

frontend/src/app/(main)/chat/Home.tsx

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the config "next/core-web-vitals" to extend from. Please check that the name of the config is correct.

The config "next/core-web-vitals" was referenced from the config file in "/frontend/.eslintrc.json".

If you still have problems, please stop by https://eslint.org/chat/help to chat with the team.

frontend/src/app/(main)/chat/layout.tsx

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the config "next/core-web-vitals" to extend from. Please check that the name of the config is correct.

The config "next/core-web-vitals" was referenced from the config file in "/frontend/.eslintrc.json".

If you still have problems, please stop by https://eslint.org/chat/help to chat with the team.

• 10 others

---

📜 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 69a6960 and 0a1361b.

⛔ Files ignored due to path filters (1)

• frontend/src/app/favicon.ico is excluded by !**/*.ico

📒 Files selected for processing (13)

• frontend/src/app/(main)/chat/Home.tsx (1 hunks)
• frontend/src/app/(main)/chat/MainLayout.tsx (2 hunks)
• frontend/src/app/(main)/chat/layout.tsx (1 hunks)
• frontend/src/app/(main)/page.tsx (1 hunks)
• frontend/src/app/hooks/useModels.ts (1 hunks)
• frontend/src/app/layout.tsx (1 hunks)
• frontend/src/components/SignInModal.tsx (1 hunks)
• frontend/src/components/chat/chat-bottombar.tsx (1 hunks)
• frontend/src/components/chat/chat-list.tsx (1 hunks)
• frontend/src/components/chat/chat-topbar.tsx (1 hunks)
• frontend/src/components/code-engine/project-context.tsx (1 hunks)
• frontend/src/components/ui/sidebar.tsx (1 hunks)
• frontend/src/components/user-settings.tsx (1 hunks)

✅ Files skipped from review due to trivial changes (9)

• frontend/src/components/SignInModal.tsx
• frontend/src/components/chat/chat-list.tsx
• frontend/src/components/chat/chat-topbar.tsx
• frontend/src/components/code-engine/project-context.tsx
• frontend/src/components/ui/sidebar.tsx
• frontend/src/app/layout.tsx
• frontend/src/components/chat/chat-bottombar.tsx
• frontend/src/app/hooks/useModels.ts
• frontend/src/app/(main)/chat/MainLayout.tsx

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Install and Build Frontend

🔇 Additional comments (7)

frontend/src/components/user-settings.tsx (1)

18-18: Import path updated to reflect reorganized directory structure.

The import path for the useAuth hook has been updated from @/hooks/useAuth to @/app/hooks/useAuth, aligning with the broader pattern of moving hooks to the app directory.

frontend/src/app/(main)/chat/layout.tsx (1)

1-2: Import changes align with naming convention standardization.

Two changes were made:

1. Added type imports (Metadata, Viewport) from 'next', which may be useful for future metadata configuration
2. Updated import path for MainLayout to use PascalCase naming convention, which is more consistent with React component naming standards

These changes improve code consistency without affecting functionality.

frontend/src/app/(main)/page.tsx (1)

9-12: Component imports standardized to PascalCase and path updated.

The changes:

1. Updated modal component imports to use PascalCase naming conventions (SignUpModal, SignInModal, AuthChoiceModal)
2. Changed the useAuthContext import path from an absolute path (@/providers/AuthProvider) to a relative path (../providers/AuthProvider)

These changes align with React naming conventions and reflect the reorganized directory structure.

frontend/src/app/(main)/chat/Home.tsx (4)

3-9: Added useContext import from React.

The useContext hook has been added to the React imports, suggesting potential usage of React context. However, I don't see any implementation using this hook in the component.

Ensure that useContext is being used somewhere in this component, or consider removing the unused import.

---

17-17: Added useMutation import from Apollo Client.

The useMutation hook has been added alongside the existing useQuery import, indicating possible future mutation operations. However, I don't see any implementation using this hook in the component.

Verify that useMutation is being used somewhere in this component, or consider removing the unused import.

---

20-22: Updated import paths for hooks to reflect new directory structure.

The import paths for useModels, useChatList, and useChatStream have been updated to use a shorter relative path (../../hooks/ instead of ../../../hooks/), aligning with the reorganized directory structure.

---

25-25: Added ProjectContext import without apparent usage.

A new import for ProjectContext has been added, but I don't see it being used in the component. This might be preparation for future functionality.

Verify that ProjectContext is being used in the component or consider removing the unused import.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • 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.
• @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.