chore(webapp): adds 200% and 500% billing alert options

[samejr]

Includes 200% and 500% options in the billing alerts (checked by default) to help prevent surprise bills

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3c7750a

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

The change updates a single route file by expanding the predefined alert threshold options used to render checkbox selections for billing alerts. The checkboxLevels array now includes 2.0 and 5.0 in addition to existing values [0.75, 0.9, 1.0]. The rendering logic continues to map these levels into CheckboxWithLabel components, with defaultChecked derived from alerts.alertLevels and display values computed as level * 100 for percentages and used in the existing currency calculation. No other control flow, data fetching, or component interfaces are modified.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description provides a clear explanation of what changed and why (adding 200% and 500% billing alert options to prevent surprise bills), along with a helpful screenshot demonstrating the UI change. However, it is missing several required sections from the template including the issue reference (Closes #), the checklist with contributing guide confirmation and PR title convention verification, the Testing section describing test steps, and a formal Changelog section. While the description conveys the core change effectively, it does not follow the repository's required template structure.	To meet the repository requirements, add the missing template sections: include "Closes #" if this addresses a specific issue, complete the checklist confirming you followed the contributing guide and tested the code, add a Testing section describing how you verified the new 200% and 500% alert options work correctly (e.g., "Verified that the new alert threshold options appear in the UI, are checked by default, and correctly display the percentage values"), and include a Changelog entry summarizing the change (e.g., "Added 200% and 500% billing alert threshold options to help prevent surprise bills").
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The pull request title "Adds 200 and 500 % billing alert options" accurately and concisely describes the main change in the changeset. The code modification expands the checkboxLevels array from [0.75, 0.9, 1.0] to [0.75, 0.9, 1.0, 2.0, 5.0], which directly corresponds to adding 200% and 500% alert options in the billing alerts UI. The title is clear, specific, and directly related to the primary purpose of the change, making it easy for teammates to understand what was modified when scanning through the commit history.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore(webapp)-add-200-and-500-percent-billing-alerts

---

📜 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 ddebe4d and 8259739.

📒 Files selected for processing (1)

• apps/webapp/app/routes/_app.orgs.$organizationSlug.settings.billing-alerts/route.tsx (1 hunks)

🧰 Additional context used

📓 Path-based instructions (3)

**/*.{ts,tsx}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

**/*.{ts,tsx}: Always prefer using isomorphic code like fetch, ReadableStream, etc. instead of Node.js specific code
For TypeScript, we usually use types over interfaces
Avoid enums
No default exports, use function declarations

Files:

• apps/webapp/app/routes/_app.orgs.$organizationSlug.settings.billing-alerts/route.tsx

{packages/core,apps/webapp}/**/*.{ts,tsx}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

We use zod a lot in packages/core and in the webapp

Files:

• apps/webapp/app/routes/_app.orgs.$organizationSlug.settings.billing-alerts/route.tsx

apps/webapp/**/*.{ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/webapp.mdc)

When importing from @trigger.dev/core in the webapp, never import the root package path; always use one of the documented subpath exports from @trigger.dev/core’s package.json

Files:

• apps/webapp/app/routes/_app.orgs.$organizationSlug.settings.billing-alerts/route.tsx

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (23)

• GitHub Check: units / internal / 🧪 Unit Tests: Internal (5, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (6, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (8, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (7, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (2, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (6, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (3, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (4, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (4, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (5, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (1, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (7, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (1, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (8, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (3, 8)
• GitHub Check: units / packages / 🧪 Unit Tests: Packages (1, 1)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (2, 8)
• GitHub Check: e2e / 🧪 CLI v3 tests (ubuntu-latest - pnpm)
• GitHub Check: e2e / 🧪 CLI v3 tests (ubuntu-latest - npm)
• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - npm)
• GitHub Check: typecheck / typecheck
• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - pnpm)
• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (1)

apps/webapp/app/routes/_app.orgs.$organizationSlug.settings.billing-alerts/route.tsx (1)

184-184: Verify backend defaults for new thresholds

The frontend change correctly adds the 200% and 500% threshold options to the checkboxLevels array. However, the defaultChecked state (line 268) derives from alerts.alertLevels returned by the backend.

The backend implementation resides in the external @trigger.dev/platform package (version 1.0.18), which is outside this repository. To ensure new thresholds are checked by default for existing users—as stated in the PR objectives—verify that the platform service includes 2.0 and 5.0 in the alertLevels array when returning billing alerts, particularly for organizations that haven't explicitly configured these values yet.

---

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

Tip

🧪 Early access (models): enabled

We are currently testing Sonnet 4.5 code review models, which should lead to better review quality. However, this model may result in higher noise levels in the review comments. Please disable the early access features if the noise level causes any inconvenience.

Note:

• Public repositories are always opted into early access features.
• You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}