Improve supervisor change integration #114
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "supervisor-change-daisy-integration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Previously when we wanted to change supervisor we had to make two calls against the daisy api.
A DELETE and a POST, this was brittle because if one of the calls failed we didn't have a good way of handling that.
This could leave the application in a state where a project could end up with 2 different supervisors.
This caused side effects and forced us to manually go into the databases and clean up the errors.
Now the daisy api is updated and we only need to do a POST to change the supervisor. See further documentation here
POST /thesis/{id}/contributor
IMPORTANT: Release needs to be synced with Daisy API
Improve supervisor change integrationto WIP: Improve supervisor change integrationCode looks good. Nice to get closer to full
java.time
utilization by removing usages ofjava.util.Calendar
.Has this been tested against the new version of Daisy's API and that start date, end date, and supervisor is updated correctly? As in - is this ready for a synced release?
Have not tested with the new version of Daisy's API, i could use some help with doing that.
But the new xsd and date changes where tested in conjunction with #113 . We decided to have those changes in conjunction with this fix instead as per our discussion.
WIP: Improve supervisor change integrationto Improve supervisor change integrationTested against daisys API seems to work as expected