Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement check in setFreeMonth to prevent multiple free months for users #321

Open
sourcery-ai bot opened this issue Dec 4, 2024 · 1 comment
Open
Assignees

Comments

@sourcery-ai
Copy link

sourcery-ai bot commented Dec 4, 2024

The setFreeMonth function currently lacks a mechanism to verify if a user has already utilized their free month. This oversight allows users to potentially exploit the system by obtaining multiple free months. To address this, we need to implement a check within the setFreeMonth function that verifies a user's usage history to ensure they have not previously used their free month.

The intended behavior is that each user should only be eligible for one free month, regardless of the number of referrals they make. As an alternative incentive for users who refer others, we can consider offering discounts or other gifts, but not additional free months.

Action Items:

  1. Update the setFreeMonth function to include a check for the user's free month usage history.
  2. Ensure that the system correctly identifies users who have already used their free month and prevents them from receiving another.
  3. Consider implementing alternative rewards for users who refer others, such as discounts, instead of additional free months.

I created this issue for @AndlerRL from #320 (comment).

Tips and commands

Interacting with Sourcery

  • Generate a plan of action: Comment @sourcery-ai plan on this issue.
  • Generate a pull request for this issue: Comment @sourcery-ai develop to
    generate a PR that addresses this issue.

Getting Help

@AndlerRL
Copy link
Contributor

AndlerRL commented Dec 4, 2024

@sourcery-ai plan

@Bran18 Bran18 self-assigned this Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants