Feature/membership system refractor #220
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…membership, and deducting mappi balance
…ship, and deduct mappi
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Membership API operations + results [via Swagger UI]
|
|
Transaction API operations + results [via Swagger UI]
|
|
Hi @DarinHajou - could you please review the latest and finalized PR updates and approve if you agree with the changes? Please let me know otherwise. In the meantime, I'll be reviewing your FE changes and make PR adjustments for that to work with the updated BE. Thx! |
…com/map-of-pi/map-of-pi-backend-react into feature/membership-system-refractor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR refactors the membership system to use its own Membership model instead of relying on UserSettings. Membership details like membership_class, mappi_balance, and membership_expiration are now managed independently, with pi_uid as the key identifier.
The Tiers model is still used to define membership tiers. This implementation is cleaner and more focused. Next up is integrating the frontend UI and handling payments with the Pi SDK.