There's technically still one bug. Deleting an appointment_type requires a different process because of how the database is set up, and right now the lambda returns a 200 OK instead of a 404 Not Found when called on an appointment_type that has already been deleted. The actual functionality is the same and this is a use case that probably won't show up anyway, so I didn't feel that it was worth it to do an entire extra query/check to get the proper response.
There's technically still one bug. Deleting an appointment_type requires a different process because of how the database is set up, and right now the lambda returns a 200 OK instead of a 404 Not Found when called on an appointment_type that has already been deleted. The actual functionality is the same and this is a use case that probably won't show up anyway, so I didn't feel that it was worth it to do an entire extra query/check to get the proper response.