Closed sufyanAbbasi closed 3 months ago
@rfontanarosa PTAL?
Ah, I think I have a picture for what's going on here... the trigger for updating /jobs
is not happening when you hit "Continue" after the initial job configuration screen, it only triggers on survey title update because of the updateSurvey
callback which does:
await Promise.all(jobs.map(job => this.updateJob(surveyId, job)));
Or if we publish changes after an edit.
So in order to properly save the jobs in proto at the initial configuration, we have to trigger an updateSurvey
when we hit Continue
or something?
Gentle ping @rfontanarosa
I think I found the bug! On "Continue" we run saveTasks()
which doesn't call updateJob()
which does the routine to serialize the tasks to proto. Maybe we can pull that logic in there?
Describe the bug Not all tasks are being converted to proto for some reason.
To Reproduce Steps to reproduce the behavior:
npm run start:local
(localhost:5000)Expected behavior There should be 9 task protos for each task type.
Screenshots