For removal of major objects, issue a warning message of the consequences and ask user to confirm

[edwardUL99]

When removing objects from the database that contain a lot of information about them, e.g. modules as they contain students, grades, exams, etc. issue a warning of the consequences of that deletion action and ask the user if they still want to continue

This is going to be broken down into a number of sub-tasks for each item:

Some of these may not be allowed to be deleted if there are foreign key restrictions (this could cause crashes if not handled)

For each of these check schema, and if necessary, open new issues to resolve any issues with them that need to be handled in this repository or Libraru

• [x] Course - This contains Modules, Lecturers and Students (maybe issue more than 1 warning/confirmation request)

• [x] Module - Contains Students, Exams, Grades, Announcements (maybe more than 1 warning/confirmation request)

• [x] Student - Contains grades (2 warnings required)

• [x] Lecturer - Contains Modules (maybe more than 1 warning/confirmation request)

• [x] Exams - Contains grades (1 warning/confirmation request)

[edwardUL99]

An idea could be a method confirmRemoval in UIUtils which takes the message to print and number of times to confirm (possibly then an array of strings to display on each confirmation) and then return true if you definitely want to cancel, false if not. Then the caller can abort if it returns false

[edwardUL99]

Added a helper function confirmRemoval where you pass it the removal message and number of times to confirm and it does the rest of the work then. This is useful for the other sub-tasks as allows you to now confirm removal for others with minimal repetition of code. Just define the message to display i.e. what removing this object will result in removal of others, and the number of times to confirm and if it returns true continue with removal, if false, abort