Skip to content

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

Closed
wants to merge 17 commits into from
Closed

Feature/membership system #214

wants to merge 17 commits into from

Conversation

DarinHajou
Copy link
Member

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.

@DarinHajou DarinHajou requested review from swoocn and adisa39 December 6, 2024 21:36
@DarinHajou DarinHajou self-assigned this Dec 6, 2024
Copy link

vercel bot commented Dec 6, 2024

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

Name Status Preview Comments Updated (UTC)
map-of-pi-backend-react ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 6, 2024 9:38pm

@swoocn
Copy link
Member

swoocn commented Dec 8, 2024

A bit confused @DarinHajou - so did we not decide to go with a separate Membership model as per the updated DB schema document?

image

@@ -54,8 +54,26 @@ const userSettingsSchema = new Schema<IUserSettings>(
required: false,
default: [0, 0]
},
},
Copy link
Member

@swoocn swoocn Dec 8, 2024

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..

Copy link
Member

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?

@swoocn
Copy link
Member

swoocn commented Feb 23, 2025

This PR is superseded by #220.

@swoocn swoocn closed this Feb 23, 2025
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

Successfully merging this pull request may close these issues.

2 participants