refactor: use Next.js API route instead of direct backend request

[opahopa]

No description provided.

[coderabbitai]

Summary by CodeRabbit

• Refactor
  • Streamlined backend page crawling by switching from a direct URL-based request to an integrated API endpoint.
  • Eliminated manual environment-based configurations while maintaining robust error handling and response processing.

Walkthrough

The change updates how the application handles the crawling request. The previous implementation constructed a backend API URL using environment variables and made a direct call. In the new implementation, the fetch request now directly targets the Next.js API route /api/crawl. The modifications remove the environment variable checks and direct logging related to the backend URL, while preserving the error handling and response processing logic.

Changes

File	Change Summary
app/page.tsx	Replaced direct fetch to a backend API (with URL constructed from env variables) with a fetch to /api/crawl. Removed URL construction and logging lines; kept error handling and response processing unchanged.

Sequence Diagram(s)

sequenceDiagram
    participant Client as Browser
    participant Page as app/page.tsx
    participant API as Next.js API Route (/api/crawl)

    Client->>Page: Initiates page load / crawl request
    Page->>API: Fetch crawl data via `/api/crawl`
    API-->>Page: Return response or error
    Page-->>Client: Render data / handle error

Loading

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 20edbea and a392f91.

📒 Files selected for processing (1)

• app/page.tsx (1 hunks)

🔇 Additional comments (1)

app/page.tsx (1)

171-174: Consistent refactoring to use Next.js API route

The change appropriately replaces a direct backend request with a Next.js API route, which aligns with modern Next.js best practices. This simplifies the code by removing environment variable dependencies while maintaining the same functionality.

Advantages of this approach:

• Simplifies configuration by eliminating environment variable requirements
• Provides better encapsulation of backend communication
• Maintains consistent pattern with the discovery endpoint at line 51

The error handling and response processing remain intact, ensuring no regression in functionality.

✨ Finishing Touches

• 📝 Docstrings were successfully generated. (🔄 Check again to generate docstrings again)

---

🪧 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 plan to trigger planning for file edits and PR creation.
• @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 or @cyberagi-AI summarize to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai or @cyberagi-AI 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.

[coderabbitai]

Note

Generated docstrings for this pull request at #46