-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: trigger bug fixes #36
Conversation
const jobCreated = await this.jobManagerClient.create(workerInput); | ||
return jobCreated; | ||
} else if (duplicationExist.status === OperationStatus.COMPLETED) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i would have written
if (duplicationExist && duplicationExist.status === OperationStatus.COMPLETED) { // for completed
const completeResponseData = duplicationExist as ICallbackResponse;
completeResponseData.bbox = bbox;
return duplicationExist;
} else if (duplicationExist) { // for in progress
return duplicationExist;
}
// else rest of the code (not duplicationExist) without an if
const batches: ITileRange[] = [];
for (let i = 0; i <= zoomLevel; i++) {
...
...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
return duplicationExist; | ||
} else if (duplicationExist) { | ||
return duplicationExist; | ||
} else { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you don't need the "else { " condition - remove it as it's obvious
updating logic for returning callbacks on case of existing (naive cache)
scenarios:
Send GPKG request
1.No job is in progress with those parameters - create new
2.Job is In progress - return “In Progress“
3.Job completed not cleaned return callback response
4.Job completed - cleaned - same as “a”
Bug fixes: