🗃️ Add subscription interval enum

[lukevella]

Summary by CodeRabbit

• New Features

  • Introduced a new subscription interval type with options for daily, weekly, monthly, and yearly selections, improving clarity in subscription management.

• Refactor

  • Updated the subscription model to enforce stricter type constraints on interval selections, enhancing validation and consistency.

• Chores

  • Backend improvements implemented to utilize validated interval selections, enhancing data accuracy and system stability.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
app	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 21, 2025 11:45am
landing	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 21, 2025 11:45am

[coderabbitai]

Walkthrough

This pull request introduces a new enum type to handle subscription intervals. The migration script creates the subscription_interval enum with values 'day', 'week', 'month', and 'year', adds a temporary column interval_enum to convert existing data, enforces a NOT NULL constraint, and replaces the old interval column with the new enum type. Additionally, the Prisma schema is updated to map the interval field in the Subscription model from a string to the new SubscriptionInterval enum, ensuring type safety and stricter data validation.

Changes

File(s)	Summary
packages/database/prisma/migrations/.../migration.sql	Introduces the new subscription_interval enum, adds a temporary interval_enum column to the subscriptions table, migrates data using a CASE statement, applies NOT NULL, drops the old column, and renames interval_enum to interval.
packages/database/prisma/schema.prisma	Adds the SubscriptionInterval enum (mapped to subscription_interval) and updates the Subscription model by changing the interval field from a String to the new enum type.

Sequence Diagram(s)

sequenceDiagram
    participant MS as Migration Script
    participant DB as Subscriptions Table

    MS->>DB: Add temporary column `interval_enum`
    MS->>DB: Read values from existing `interval`
    MS->>DB: Update `interval_enum` using CASE statement
    MS->>DB: Enforce NOT NULL on `interval_enum`
    MS->>DB: Drop the old `interval` column
    MS->>DB: Rename `interval_enum` to `interval`

Loading

Possibly related PRs

• 🗃️ Make subscription fields required #1565: Modifies the enforcement of the NOT NULL constraint on the interval field in the subscriptions table, aligning closely with the changes implemented in this migration.

Poem

I'm a hopping rabbit with a coder's delight,
Changing strings to enums makes my day so bright.
Month and year now in a neat new dance,
Data flows smoothly, given a second chance.
I nibble on code and celebrate this feat—
With carrots and joy, the migration is sweet!

---

📜 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 9ac2760 and 6d5fcba.

📒 Files selected for processing (2)

• packages/database/prisma/migrations/20250221111248_add_subscription_interval_enum/migration.sql (1 hunks)
• packages/database/prisma/schema.prisma (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• packages/database/prisma/migrations/20250221111248_add_subscription_interval_enum/migration.sql

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

• GitHub Check: Unit tests
• GitHub Check: Integration tests
• GitHub Check: Type check
• GitHub Check: Linting

🔇 Additional comments (2)

packages/database/prisma/schema.prisma (2)

76-83: New Enum Declaration:
The new SubscriptionInterval enum is correctly declared with the values day, week, month, and year and is mapped to "subscription_interval" using @@map. This effectively reinforces type safety for subscription intervals. Please ensure that your migration script remains synchronized with this schema change to correctly convert and validate the existing data.

---

98-110: Updated Subscription Model - Interval Field:
The interval field within the Subscription model now uses the SubscriptionInterval enum instead of a regular String. This change improves data integrity by enforcing strict allowed values. Please verify that all parts of your application that interact with this field have been updated to handle the enum, and that the migration correctly converts existing interval data.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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. (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.