Currently, as of #55, making a GET request to the appointmentSlots endpoint returns all appointments the hospital. Instead we should require that the user specifies a start and end date so we don't inundate the front end with unnecessary data.
@bl-nero An alternative to this solution I just thought of is to return only available appointments. Should we stick with this or should we have a GET to appointmentSlots return all the available appointments?
Currently, as of #55, making a GET request to the appointmentSlots endpoint returns all appointments the hospital. Instead we should require that the user specifies a start and end date so we don't inundate the front end with unnecessary data.
@bl-nero An alternative to this solution I just thought of is to return only available appointments. Should we stick with this or should we have a GET to appointmentSlots return all the available appointments?