-
Notifications
You must be signed in to change notification settings - Fork 3
reservation routes in protected api client #31
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
Conversation
jackblanc
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work! Take a look at the authClient.test.ts for a guide on how to test this, it should be pretty simple but I think it's worth having.
You may need to include .then.catch chains to resolve the promises... honestly not too sure. We can cross that bridge when we use these.
|
The fail_qa route is not recognized. Not sure why |
|
|
||
| const BASE_URL = 'http://localhost'; | ||
|
|
||
| // TODO: handle invalid cases |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add a ticket for this on Monday on the bugs/tech debt section? Don't want this to get lost. Or finish it as part of this PR.
jackblanc
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, we love tests :)
Why
Monday.com Ticket
This PR connects the reservation routes to the frontend to allow users to connect to the sftt backend and edit the status of blocks
This PR
Added a new protected API client file and added each of the routes and functions. Followed the same pattern as the routes made by @jackblanc in LLB.
Verification Steps
The UI for the reservation pages is not fully set up so I have not been able to confirm that everything is working as expected.