1. Implementation of the audit list component page
Copy and paste on the front end to modify the code in the appointment list
We only return the data to be reviewed here, so when the front end sends a request to the back end, it will explain to the back end that all we want is the book_state value that needs to be reviewed.
Let’s create an expiration date and see if it will show up in the review list
There are no reservations for October 4th.
2. Implementation of the approval and rejection functions of the audit list component
2.1. Front-end
Click Update to change status
After we get the audit data AUDIT: 0, click to approve and pass in an APPROVE: 1, click to reject and pass in a REJECT: 2, then the handleUpdate method receives the id and splices it up, and what is brought over is book_state. 1 or 2. If the update is successful, getList.
Front-end self-test
2.2. Backend
