-
Notifications
You must be signed in to change notification settings - Fork 3
Feature/membership payment final #261
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
base: dev
Are you sure you want to change the base?
Conversation
…membership, and deducting mappi balance
…ship, and deduct mappi
I'll be pushing some adjustments to your PR @DarinHajou; stay tuned! |
…/map-of-pi/map-of-pi-backend-react into feature/membership-payment-final
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.
Nice! But the script can certainly be optimized to eliminate the N+1 queries.
const { membership_class, membership_duration, mappi_allowance } = req.body; | ||
|
||
// Basic input validation | ||
if ( |
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.
We could potentially use a schema validator to reduce manual validation and improve leverage across our controllers. 🤫
This PR includes a lot of changes that will conflict with the Order and Payment updates in Haycoder’s PR. I think it would be more efficient to prioritize reviewing his PR first, then revisit yours afterward to minimize merge issues. Thanks for your patience—please hold off for now @DarinHajou. |
Unknown entity; not on the Map of Pi Dev team.
…/map-of-pi/map-of-pi-backend-react into feature/membership-payment-final
This branch (feature/membership-payment-final) builds directly on top of feature/membership-system-refactor, finalizing the U2A Pi payment flow for membership upgrades. All the main logic is in place, including the controller, model updates, and route setup.
It’s functional, but I’d suggest handling edge cases like duplicate payments and late completions in a separate branch to keep this one focused and clean.