makes new endpoint /level which returns the emails, chat history and defences for a given level
deletes the now unused endpoints that get the email, chat history and defences individually
renames the existing levelService to resetService (because all it was doing was resetting a level)
adds new levelService for accessing our new endpoint
Further PRs
I notice that we pass the entire defences object to the front end when switching to and loading up levels 1 and 2. However we don't use any of this information unless we're showing it in the ControlPanel. Which is both confusing to read and also a waste of bandwidth. To fix this I think would warrant a separate PR.
There is also the problem of having lots of getModel calls when we switch to sandbox. That can also be a separate PR
Description
combines the change level network calls into one
Notes
levelService
toresetService
(because all it was doing was resetting a level)levelService
for accessing our new endpointFurther PRs
Concerns
Checklist
Have you done the following?