feat: $199 pricing model for unlimited plans

[ShubhamPalriwala]

What does this PR do?

Introduce new plan for the unlimited offering and update accordingly in Stripe

Type of change

• Enhancement (small improvements)

Checklist

Required

• Filled out the "How to test" section in this PR
• Read How we Code at Formbricks
• Self-reviewed my own code
• Commented on my code in hard-to-understand bits
• Ran pnpm build
• Checked for warnings, there are none
• Removed all console.logs
• Merged the latest changes from main onto my branch with git pull origin main
• My changes don't cause any responsiveness issues
• First PR at Formbricks? Please sign the CLA! Without it we wont be able to merge it 🙏

Appreciated

• If a UI change was made: Added a screen recording or screenshots to this PR
• Updated the Formbricks Docs if changes were necessary

[vercel]

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

2 Ignored Deployments

Name	Status	Preview	Comments	Updated (UTC)
formbricks-cloud	⬜️ Ignored (Inspect)	Visit Preview		Nov 3, 2023 8:24am
formbricks-com	⬜️ Ignored (Inspect)	Visit Preview		Nov 3, 2023 8:24am

[github-actions]

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

[review-agent-prime]

subscriptionCreatedOrUpdated.ts

The code has a lot of redundancy, especially in the switch-case statements where the same logic is repeated for different cases. This can be refactored by creating a function that encapsulates the common logic and takes the varying parts as parameters.

Create Issue

    async function handleProduct(productName, featureKey, unlimitedKey, unlimitedKey199, team, stripeSubscriptionObject) {
      let updatedFeatures = team.billing.features;
      if (
        !(
          stripeSubscriptionObject.cancel_at_period_end &&
          team.billing.features[featureKey].status === "cancelled"
        )
      ) {
        updatedFeatures[featureKey].status = "active";
      }
      if (
        item.price.lookup_key === unlimitedKey ||
        item.price.lookup_key === unlimitedKey199
      ) {
        updatedFeatures[featureKey].unlimited = true;
      } else {
        const countForTeam = await getMonthlyTeamResponseCount(team.id);
        await reportUsage(
          stripeSubscriptionObject.items.data,
          featureKey,
          countForTeam
        );
      }
      return updatedFeatures;
    }

    for (const item of stripeSubscriptionObject.items.data) {
      const product = await stripe.products.retrieve(item.price.product as string);
      switch (product.name) {
        case StripeProductNames.inAppSurvey:
          updatedFeatures = await handleProduct(StripeProductNames.inAppSurvey, ProductFeatureKeys.inAppSurvey, StripePriceLookupKeys.inAppSurveyUnlimited, StripePriceLookupKeys.inAppSurveyUnlimited199, team, stripeSubscriptionObject);
          break;
        case StripeProductNames.linkSurvey:
          updatedFeatures = await handleProduct(StripeProductNames.linkSurvey, ProductFeatureKeys.linkSurvey, StripePriceLookupKeys.linkSurveyUnlimited, StripePriceLookupKeys.linkSurveyUnlimited199, team, stripeSubscriptionObject);
          break;
        case StripeProductNames.userTargeting:
          updatedFeatures = await handleProduct(StripeProductNames.userTargeting, ProductFeatureKeys.userTargeting, StripePriceLookupKeys.userTargetingUnlimited, StripePriceLookupKeys.userTargetingUnlimited199, team, stripeSubscriptionObject);
          break;
      }
    }

The code throws generic Error objects with a message string. This is not ideal for error handling because it does not provide much context about the error. It would be better to create custom error classes that can carry more information about the error.

Create Issue

    class TeamNotFoundError extends Error {
      constructor() {
        super("Team not found");
        this.name = "TeamNotFoundError";
      }
    }

    // Usage
    if (!team) {
      throw new TeamNotFoundError();
    }

page.tsx

The code throws generic Error objects with a message string. This is not ideal for error handling because it does not provide much context about the error. It would be better to create custom error classes that can carry more information about the error.

Create Issue

    class UnauthorizedError extends Error {
      constructor() {
        super("Unauthorized");
        this.name = "UnauthorizedError";
      }
    }

    class TeamNotFoundError extends Error {
      constructor() {
        super("Team not found");
        this.name = "TeamNotFoundError";
      }
    }

    // Usage
    if (!session) {
      throw new UnauthorizedError();
    }

    if (!team) {
      throw new TeamNotFoundError();
    }

checkoutSessionCompleted.ts

The code throws generic Error objects with a message string. This is not ideal for error handling because it does not provide much context about the error. It would be better to create custom error classes that can carry more information about the error.

Create Issue

    class TeamNotFoundError extends Error {
      constructor() {
        super("Team not found");
        this.name = "TeamNotFoundError";
      }
    }

    // Usage
    if (!team) {
      throw new TeamNotFoundError();
    }

[mattinannt]

💪🙏