Migrated from Clearbit to logo.dev

[sahitya-chandra]

Linked Issue(s)

fixes #641

Migrated from using logo.clearbit.com to https://www.logo.dev/

Summary by CodeRabbit

• Chores
  • Removed the routing for organization logos, which eliminates access to the previous logo service.

[coderabbitai]

Walkthrough

This change removes a rewrite rule in the Next.js configuration file. The rule that redirected requests from the source path /org-logo/:path* to the destination https://logo.clearbit.com/:path* has been deleted, altering the routing behavior for requests matching the specified source path. No other entity declarations were modified.

Changes

File(s)	Change Summary
web-server/next.config.js	Removed the rewrite rule redirecting from /org-logo/:path* to https://logo.clearbit.com/:path*

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant S as Next.js Server
    U->>S: Request /org-logo/company.png
    S-->>U: 404 Not Found (no logo service available)

Loading

Assessment against linked issues

Objective	Addressed	Explanation
Replace usage of Clearbit Logo API with alternative service (#641)	✅

Poem

I'm a rabbit in the code, so spry and keen,
Hopping through URLs, keeping systems clean.
The Clearbit path's gone, a new route we seek,
In the garden of code, fresh solutions we tweak.
With a leap and a bound, to the future we race,
Embracing the change, in this digital space! 🐇✨

---

📜 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 3945fd4 and c3aa061.

📒 Files selected for processing (1)

• web-server/next.config.js (0 hunks)

💤 Files with no reviewable changes (1)

• web-server/next.config.js

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

• GitHub Check: All file linting

---

🪧 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 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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b715c16 and 2d45f4b.

📒 Files selected for processing (1)

• web-server/next.config.js (1 hunks)

[jayantbh]

We don't seem to use the /org-logo path/api here, so we can just entirely remove it.