feat(frontend): add Apollo configuration and remove unused GraphQL queries

[Sma1lboy]

This Pull Request adds Apollo GraphQL configuration and removes unused GraphQL queries. By integrating Apollo, developers can now benefit from Language Server Protocol (LSP) support directly in VSCode by installing the Apollo GraphQL extension. This provides enhanced features like autocompletion, validation, and schema awareness when working with GraphQL queries, making development more efficient and reducing errors.

Summary by CodeRabbit

• Chores
  • Introduced an updated GraphQL client configuration for improved service connectivity.
• Refactor
  • Removed legacy data operations and obsolete code pathways to streamline internal processes.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes introduce a new Apollo Client configuration file that sets up the service name, schema file path, and source file patterns. In addition, an unused Chat type import has been removed from a sidebar component. Several GraphQL operations and helper functions related to chat history and project details have been deleted from the GraphQL request file, reducing unused or legacy functionality.

Changes

File(s)	Summary
frontend/apollo.config.js	Added new Apollo Client configuration with service name 'codefox-backend1', schema file path, and source file inclusion/exclusion settings.
frontend/src/components/file-sidebar.tsx; frontend/src/graphql/request.ts	Removed unused Chat import; deleted GraphQL operations (SAVE_CHAT_HISTORY, GET_PROJECT_DETAILS) and related functions (getProjectDetails, createProject).

Sequence Diagram(s)

sequenceDiagram
    participant App as Application
    participant Config as Apollo Configuration
    participant Schema as Local Schema File
    participant Service as GraphQL Service

    App->>Config: Load Apollo config on startup
    Config->>Schema: Read schema from './src/graphql/schema.gql'
    App->>Service: Initialize Apollo Client with config
    Service-->>App: Return GraphQL responses

Loading

Suggested reviewers

• PengyuChen01
• ZHallen122

Poem

Hoppin' through code with a joyful beat,
I found fresh configs oh so neat.
Unused chatter has hopped away,
Leaving clean paths for a brighter day.
With ASCII hops and carrot dreams,
I celebrate changes in code extremes!
🐰✨

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/apollo.config.js

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.

---

📜 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 17611fe and eb3f020.

📒 Files selected for processing (3)

• frontend/apollo.config.js (1 hunks)
• frontend/src/components/file-sidebar.tsx (0 hunks)
• frontend/src/graphql/request.ts (0 hunks)

---

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.