In this PR, I added an Admin Review Form (plus its tests and stories) for Rider Applications such that:
Admins can see applications with buttons like "Approve", "Deny", and "Save".
All three buttons ("Approve", "Deny", "Save") save any edits made to the response field.
The "Approve" or "Deny" buttons can change the status of the application to "Accepted" or "Declined" respectively.
There's also a "Return without Saving" button, which redirects to the "/admin/applications/riders" page without saving any changes to the form.
For Accepted Applications:
Admins can see applications with a button called "Set Status to Expired" on the "/admin/applications/riders/review/:id" page.
There's also a "Return without Saving" button.
In this case, the notes field is editable.
Clicking the "Set Status to Expired" button updates the status to "Expired" and saves the changes.
Clicking "Return without Saving" returns to the "/admin/applications/riders" page, discarding any changes made to the form.
Your form effectively manages the lifecycle of applications, providing admins with intuitive buttons and functionalities based on the application's status.
In this PR, I added an Admin Review Form (plus its tests and stories) for Rider Applications such that:
Admins can see applications with buttons like "Approve", "Deny", and "Save". All three buttons ("Approve", "Deny", "Save") save any edits made to the response field. The "Approve" or "Deny" buttons can change the status of the application to "Accepted" or "Declined" respectively. There's also a "Return without Saving" button, which redirects to the "/admin/applications/riders" page without saving any changes to the form. For Accepted Applications:
Admins can see applications with a button called "Set Status to Expired" on the "/admin/applications/riders/review/:id" page. There's also a "Return without Saving" button. In this case, the notes field is editable. Clicking the "Set Status to Expired" button updates the status to "Expired" and saves the changes. Clicking "Return without Saving" returns to the "/admin/applications/riders" page, discarding any changes made to the form. Your form effectively manages the lifecycle of applications, providing admins with intuitive buttons and functionalities based on the application's status.
Closes #48