-
Notifications
You must be signed in to change notification settings - Fork 3
Feature/membership system #214
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
Conversation
…membership, and deducting mappi balance
… IUserSettings type
…ship, and deduct mappi
…emove deductMappi function
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
A bit confused @DarinHajou - so did we not decide to go with a separate Membership model as per the updated DB schema document? |
@@ -54,8 +54,26 @@ const userSettingsSchema = new Schema<IUserSettings>( | |||
required: false, | |||
default: [0, 0] | |||
}, | |||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why didn't we just create a separate Membership model? 🤔
Curious about your thoughts with potential scaling down the road..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you clarify if this Tiers model is intended solely for informational purposes? If so, I don't anticipate the data needing to be changed very much and find the BE addition unnecessary overhead. Thoughts about treating the data as static content and presented on the FE.. perhaps in a JSON file?
This PR is superseded by #220. |
This PR introduces a fully functional membership system to the backend, enabling management of user tiers, balances, and membership expiration. Key changes include adding membership_class, mappi_balance, and membership_expiration fields to the UserSettings model to track and manage user membership details effectively. In addition, a dedicated Tiers model was created to define and manage membership tiers.
The backend now provides all necessary functionality to handle membership management. Next steps involve integrating it ot the frontend UI and implementing payment using the Pi SDK for upgrading membership.