fix: remove outdated and wrong quota check

[chronark]

we now have proper quotas, so this check is redundand.

If a workspace is disabled, there is already a warning in the root
layout to contact us.

Summary by CodeRabbit

• Refactor
  • Removed the upgrade prompt and subscription button from the API list view, so plan-related messages no longer appear.
  • Streamlined the display logic for a consistent and focused view of API controls.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
dashboard	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 20, 2025 7:19am
engineering	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 20, 2025 7:19am
play	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 20, 2025 7:19am
www	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 20, 2025 7:19am

[changeset-bot]

⚠️ No Changeset found

Latest commit: 42e9bea

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request removes the unpaid property and its related logic from the API components. The ApiListClient component no longer accepts or evaluates an unpaid prop, and the corresponding conditional rendering for upgrade prompts has been eliminated. Furthermore, the variable determining the unpaid status in the page file has been removed, leaving the component dependent solely on the initialData prop.

Changes

File(s)	Change Summary
.../apis/_components/api-list-client.tsx, .../apis/page.tsx	Removed the unpaid property and associated conditional logic. The ApiListClient component no longer displays the upgrade prompt, and the page no longer calculates or passes the unpaid variable.

Possibly related PRs

• fix: Removes the secondary search  #2768: Involves removal of the unpaid variable and related logic from the page, directly affecting the same component modifications.

Suggested labels

Bug, Core Team

Suggested reviewers

• mcstepp
• ogzhanolguncu
• perkinsjr

---

📜 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 898befd and 42e9bea.

📒 Files selected for processing (2)

• apps/dashboard/app/(app)/apis/_components/api-list-client.tsx (0 hunks)
• apps/dashboard/app/(app)/apis/page.tsx (1 hunks)

💤 Files with no reviewable changes (1)

• apps/dashboard/app/(app)/apis/_components/api-list-client.tsx

🧰 Additional context used

🧬 Code Definitions (1)

apps/dashboard/app/(app)/apis/page.tsx (1)

apps/dashboard/app/(app)/apis/_components/api-list-client.tsx (1) (1)

• ApiListClient (16-61)

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

• GitHub Check: Test Packages / Test ./packages/hono
• GitHub Check: Test Packages / Test ./packages/cache
• GitHub Check: Test Packages / Test ./internal/clickhouse
• GitHub Check: Build / Build
• GitHub Check: Test Go API Local / Test
• GitHub Check: Test API / API Test Local
• GitHub Check: Test Agent Local / test_agent_local
• GitHub Check: autofix
• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (1)

apps/dashboard/app/(app)/apis/page.tsx (1)

36-36: Simplified component interface - good cleanup!

The removal of the unpaid prop from the ApiListClient component call aligns with the PR objective to remove the outdated quota check. This simplifies the component interface and reduces unnecessary conditional logic. According to the PR description, users are already notified about workspace status through a warning in the root layout.

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

[github-actions]

Thank you for following the naming conventions for pull request titles! 🙏