Orders can be submitted even if 'enter email' and 'verify email' don't match
License and Copyright Notice
By submitting this issue or commenting on this issue, or contributing any content to this issue, you certify under the Developer Certificate of Origin that the content you post may be licensed under GPLv3 (for code) or CC-BY-SA 4.0 International (for non-code content).
What is the goal or the problem, and why is it important?
When a guest is submits an order, they are supposed to enter their email in 2 fields to confirm that they are typing it correctly. Our front end allows the guest to submit their order even if the two fields don't match. In normal circumstances, the submit box should be grayed out until all requirements are met, including the two email fields matching.
How are you going to acheive the goal or solve the problem?
This problem should be solved by trying out the submit button until the email fields match, (and they're not empty)
What will be produced as a result of this effort and where will it live on GitLab?
As a result, the backend won't receive requests with mismatched emails.
Give a justification of weight or due date.
This will have a weight of 2, since it can be done relatively easily now that react is gone.
Who will do it, and what will they do?
@DMacDonald4 will be responsible for this issue. They will make the changes on the branch, and rebase it back to ditch-react.
What was the outcome?
Now the sumbit button will remain disabled only if the users input email fields match eachother. If either one is mispelled, the sumbit button remains disabled. As of now, there is not check to verify if the email is a valid WNE email address however, both emails the user enters must match in order for them to sumbit their order.
Template Version 1.0.0
Diagrams
relates to #7 (closed) Assignees: @thebrainboy123 @dm364003
Should be branched off of ditch-react