Open LKASTI opened 5 months ago
latitude
, longitude
, and building
fields from the Location class
This means the
addOrOmit
method in the location controller must be edited
All listed constraints were applied except for deleting an event after certain time passed from event taking place. I did more research into this topic and found that this scenario might require additional scheduling methods for checking when an event has started, ended, and when it can be deleted.
Edit: This comment refers to the newly created issue #70
TODO: Forgot about not null constraints. Those need to be added to necessary fields...
Null-able constraint annotations added to relevant fields. More constraints can be added, such ensuring Appointment end times occurring after start times, the interval of time between the start and end time must be at least [ ] amount of time, and any other constraints needed.
There are several changes that need to be made to entity files to reflect database constraints and improve readability. These are some of the changes that I thought might be necessary:
(Any other necessary changes to be discussed)