Merged
Conversation
…he host and set up uploadPaymentQR.js
… made a reservation to the listing
…as all type of user are available to use it to get host payment QR code
Prakhar896
requested changes
Jul 31, 2024
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Overview of Changes
/getHostPaymentQRreturn you the host payment QR code image regardless what type of user you are (guest, host or admin), if you provide the correct food listinglistingID, the specific hosthostIDand your currently login jwt token for authorization. jwt token will used to verify current log in user as an alternative ifcheckUserauthorisation failed/manageGuestswhere handles upload payment QR code image (/uploadPaymentQR) and toggling of guest paid and present status (/togglePaidAndPresent)Sensitive Changes!
/getReservationroute endpoint