Bigger bitcoin toggle

[AnthonyRonning]

Summary by CodeRabbit

• Chores

  • Updated route tree generation with improved type safety and documentation
  • Added explicit route interfaces and type definitions

• Style

  • Enhanced Bitcoin payment option layout in Pricing page
  • Increased padding, icon size, and text size for improved visual clarity
  • Adjusted Switch component scale for better prominence

[coderabbitai]

Walkthrough

The pull request introduces significant enhancements to the route tree generation and styling in the frontend. The primary focus is on improving the routeTree.gen.ts file by adding more explicit type definitions, introducing new interfaces for route children, and updating route configurations with explicit id properties. Additionally, the PricingPage component receives visual refinements to the Bitcoin payment option, improving its layout and user interface presentation.

Changes

File	Change Summary
frontend/src/routeTree.gen.ts	- Added multiple interfaces: FileRoutesByFullPath, FileRoutesByTo, FileRoutesById, FileRouteTypes, AuthRouteChildren, PasswordResetRouteChildren, RootRouteChildren - Updated route definitions with explicit id properties - Modified route tree export to use _addFileChildren and _addFileTypes methods
frontend/src/routes/pricing.tsx	- Enhanced Bitcoin payment option styling - Increased padding, gap sizes, and icon dimensions - Adjusted Switch component scale

Sequence Diagram

sequenceDiagram
    participant RouteTree as Route Tree Generator
    participant Interfaces as Route Interfaces
    participant Routes as Route Definitions

    RouteTree->>Interfaces: Define new route interfaces
    Interfaces->>Routes: Apply type definitions
    Routes->>RouteTree: Generate typed route tree
    RouteTree-->>Routes: Export route configuration

Loading

Possibly related PRs

• Clarify bitcoin yearly billing #4: Modifications to the PricingPage component in the same file, improving the pricing structure and user interface

Poem

🐰 Routing Rabbit's Rhyme 🛤️

In routes we weave, with types so clear,
Interfaces dancing, the path grows near
Bitcoin's style, now sleek and bright
Our code leaps forward with pure delight!

~ CodeRabbit's Routing Poet 🚀

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

🪧 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. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

frontend/src/routes/pricing.tsx (2)

Line range hint 484-487: Consider making the offer end date configurable.

The discount offer end date is hardcoded to "January 31st". Consider moving this to a configuration or environment variable to make it easier to update.

-                                  <p className="text-xs sm:text-sm text-white/50">
-                                    Offer ends January 31st
-                                  </p>
+                                  <p className="text-xs sm:text-sm text-white/50">
+                                    Offer ends {process.env.NEXT_PUBLIC_OFFER_END_DATE}
+                                  </p>

---

Line range hint 119-124: Document the auto-enable Bitcoin toggle behavior.

Consider adding a comment to explain why the Bitcoin toggle is automatically enabled for Zaprite users, making it easier for other developers to understand this business logic.

  // Auto-enable Bitcoin toggle for Zaprite users
+ // Zaprite is our Bitcoin payment processor, so we automatically enable
+ // the Bitcoin toggle for users who have previously paid with Bitcoin
  useEffect(() => {
    if (freshBillingStatus?.payment_provider === "zaprite") {
      setUseBitcoin(true);
    }
  }, [freshBillingStatus?.payment_provider]);

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b0e545d and ff31018.

📒 Files selected for processing (2)

• frontend/src/routeTree.gen.ts (4 hunks)
• frontend/src/routes/pricing.tsx (1 hunks)

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

• GitHub Check: Cloudflare Pages

🔇 Additional comments (2)

frontend/src/routeTree.gen.ts (1)

7-9: Note: This is an auto-generated file.

The file header correctly indicates that this is auto-generated and should not be modified directly. The changes appear to be automatically generated by TanStack Router.

frontend/src/routes/pricing.tsx (1)

396-405: UI improvements enhance the Bitcoin payment toggle visibility.

The styling changes make the Bitcoin toggle more prominent and user-friendly:

• Increased padding and gaps for better spacing
• Larger Bitcoin icon and text for better visibility
• Full-scale switch component for easier interaction