Replace tools with plugins and rename Pro tier to Go tier#755
Conversation
- Renamed Settings tab and card references from 'tools' to 'plugins'. - Renamed and refactored `tool-selection-form.tsx` to `plugin-selection-form.tsx`. - Updated 'Mapping tools' copy to 'Mapping plugins' in purchase credits popup. - Updated 'map tools' description to 'map plugins' on sign-in page. - Renamed 'Pro' tier to 'Go' tier inside the app actions example prompts. Co-authored-by: ngoiyaeric <115367894+ngoiyaeric@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
|
|
Warning Review limit reached
Next review available in: 42 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
WalkthroughThe settings UI and related copy now refer to plugins instead of tools, the canned computer response uses Go-tier wording, and the service worker precache manifest is refreshed. ChangesPlugin terminology migration
Service worker precache refresh
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@app/actions.tsx`:
- Line 314: Update the QCX-Terra description string in the relevant action to
remove the space between the Markdown link text and URL, ensuring the QCX
Pricing link renders correctly.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 2989f1ee-4231-4ba4-a795-82abe21febd5
📒 Files selected for processing (7)
app/actions.tsxapp/sign-in/sign-in-component.tsxcomponents/purchase-credits-popup.tsxcomponents/settings/components/plugin-selection-form.tsxcomponents/settings/components/settings-skeleton.tsxcomponents/settings/components/settings.tsxpublic/sw.js
📜 Review details
🧰 Additional context used
🪛 ast-grep (0.44.1)
public/sw.js
[warning] Avoid using the initial state variable in setState
Context: setTimeout(t,e)
Note: [CWE-710] Improper Adherence to Coding Standards. Security best practice.
(setstate-same-var)
🔇 Additional comments (7)
public/sw.js (1)
2-2: LGTM!components/settings/components/plugin-selection-form.tsx (1)
29-33: LGTM!Also applies to: 52-82, 86-100, 115-140, 152-153
components/settings/components/settings.tsx (1)
17-17: LGTM!Also applies to: 40-42, 74-76, 88-90, 221-221, 256-263
components/settings/components/settings-skeleton.tsx (1)
11-11: LGTM!app/actions.tsx (1)
313-313: LGTM!app/sign-in/sign-in-component.tsx (1)
69-69: LGTM!components/purchase-credits-popup.tsx (1)
30-37: LGTM!
| ? `A planet computer is a proprietary environment aware system that interoperates weather forecasting, mapping and scheduling using cutting edge multi-agents to streamline automation and exploration on a planet. Available for our Pro and Enterprise customers. [QCX Pricing](https://www.queue.cx/#pricing)` | ||
| : `QCX-Terra is a model garden of pixel level precision geospatial foundational models for efficient land feature predictions from satellite imagery. Available for our Pro and Enterprise customers. [QCX Pricing] (https://www.queue.cx/#pricing)`; | ||
| ? `A planet computer is a proprietary environment aware system that interoperates weather forecasting, mapping and scheduling using cutting edge multi-agents to streamline automation and exploration on a planet. Available for our Go and Enterprise customers. [QCX Pricing](https://www.queue.cx/#pricing)` | ||
| : `QCX-Terra is a model garden of pixel level precision geospatial foundational models for efficient land feature predictions from satellite imagery. Available for our Go and Enterprise customers. [QCX Pricing] (https://www.queue.cx/#pricing)`; |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Fix the malformed QCX Pricing link.
Line 314 uses [QCX Pricing] (https://...); remove the space so the customer-facing link renders correctly.
Proposed fix
- : `QCX-Terra ... [QCX Pricing] (https://www.queue.cx/#pricing)`;
+ : `QCX-Terra ... [QCX Pricing](https://www.queue.cx/#pricing)`;📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| : `QCX-Terra is a model garden of pixel level precision geospatial foundational models for efficient land feature predictions from satellite imagery. Available for our Go and Enterprise customers. [QCX Pricing] (https://www.queue.cx/#pricing)`; | |
| : `QCX-Terra is a model garden of pixel level precision geospatial foundational models for efficient land feature predictions from satellite imagery. Available for our Go and Enterprise customers. [QCX Pricing](https://www.queue.cx/#pricing)`; |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@app/actions.tsx` at line 314, Update the QCX-Terra description string in the
relevant action to remove the space between the Markdown link text and URL,
ensuring the QCX Pricing link renders correctly.
![charliecreates[bot]](https://avatars.githubusercontent.com/in/1140780?s=60&v=4){kind=small}
There was a problem hiding this comment.
Reviewed all 7 changed files at commit 029fe157109a3776ae6240bb0899ae8376b80e95. No blocking correctness, reliability, security, data-integrity, or compatibility issues found. The rename is wired through the settings import/component, legacy model/tool tab aliases still map to plugin, and public/sw.js only refreshes generated precache assets. Existing checks showed GitGuardian and Vercel Preview Comments passing; no additional local checks were run.
|
For the plugins just in the settings renaming not inside the system |
Thank you for the feedback! I have completely reverted the file and component renames and left the sign-in and credits popup files untouched, ensuring we do not touch the system-level naming or internal dependencies. I only changed the visual user-facing labels in the settings/skeleton (such as tab labels, headings, select placeholders, and help text) from 'tools' to 'plugins' to preserve complete system stability. All checks compile and build successfully. |
…not inside the system Co-authored-by: ngoiyaeric <115367894+ngoiyaeric@users.noreply.github.com>
2 participants
Renamed all references to tools to plugins in user-facing settings, descriptions, and lists of features. Additionally updated 'Pro' tier references to 'Go' tier inside the example prompts.
PR created automatically by Jules for task 4255900712213641593 started by @ngoiyaeric
Summary by CodeRabbit
New Features
Chores