-
Notifications
You must be signed in to change notification settings - Fork 20
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
WhatsApp Link #79
Comments
Hi Mas Zain @zainfathoni, This is my first step on contributing to open source, and I'd like to work on this issue🙏, I have pushed the first commit just to save the seat 😅 but have not created the pull request draft yet, because I just read the prerequisite that it requires #75 . Is it means I have to wait for the #75 to be solved first before creating the pull request draft? |
No, as long as you understand the separation of scopes between the two issues, you can start working on this ticket and submit your draft PR first. I meant by requiring #75 that we can only close this ticket after we close #75. It is definitely okay to start both of them in parallel. Thanks for helping out, and have fun contributing to this project! 😉 |
Thank you Mas Zain, please for the guidance if I have any obstacles later on 😬🙏 |
Hi Mas Zain @zainfathoni . I have a question, on confirm page when I fill the fields for transaction, how could I retrieve courseId value?. Thank You🙏 |
Oops, yeah, it's a hole in our system at the moment, because we are still assuming that we're only supporting one course at the moment. Therefore, based on that assumption, you can try to get all the available courses in the database and get the first course, probably you can use the |
Okay Mas, Thank you |
Mas Zain @zainfathoni , i have another question. What should I do to the paymentTime field on the form? is it assigned to transaction as createdAt? or assigned for another purpose? .Thank you |
No, you should leave the After my changes on #108, it should be much easier to do so now. You just need to update the schema and update the |
Update: I just added the |
Description
Implement the WhatsApp interaction parts of the Transaction Flow. It requires #75 as a prerequisite.
Narrative
Acceptance Criteria
The
/dashboard/purchase/confirm
route should store the transaction values in the database and compose a prefilled WhatsApp link for the Member to send to the Author.Scenario 1: Compose WhatsApp Link
Step no. 6 (WhatsApp Link) in the Transaction Flow diagram.
Modal Content
Data transaksi tersimpan
Silakan klik tombol di bawah ini untuk mengirimkan pesan WhatsApp kepada kami. Setelah itu, tolong lampirkan bukti transfer berupa foto atau file PDF ke nomor WhatsApp tersebut. Terima kasih.
[ Kirim Pesan WhatsApp ]
WhatsApp Link
`https://api.whatsapp.com/send?phone=${authorPhoneNumber}&text=%5BKelas%20Tahun%20Prasekolahku%5D%0A%0AKlik%20di%20sini%20untuk%20verifikasi%20pembayaran%0Ahttps%3A%2F%2Frbagi.id%2Fverify%2F${transactionId}%0A%0ABerikut%20terlampir%20foto%2Ffile%20bukti%20pembayaran%20saya%3A`
P.S. I populated that link above through https://create.wa.link, you can try experimenting with it to provide a better WhatsApp message
/dashboard/purchase/confirm
route correctly,Implementation Model
Image previews
Centered with single action
Desktop view
Mobile view
Code snippets
Centered with single action
Tasks
/dashboard/purchase/verify/$transactionId
route upon a successful response/dashboard/purchase/verify/$transactionId.tsx
file/dashboard/purchase/verify.tsx
file to render the modal aboveThe text was updated successfully, but these errors were encountered: