OAPI: rename job status requeued to requeueing

Rename job status `requeued` to `requeueing`, because it indicates a
process that's (if things are working well) happening currently.
This commit is contained in:
Sybren A. Stüvel 2022-05-19 17:22:35 +02:00
parent 1aed4bf729
commit 507985e258
2 changed files with 7 additions and 8 deletions

View File

@ -782,7 +782,7 @@ components:
- archived - archived
- archiving - archiving
- cancel-requested - cancel-requested
- requeued - requeueing
- under-construction - under-construction
TaskStatus: TaskStatus:

View File

@ -32,13 +32,12 @@ export default {
const numTasks = 1; const numTasks = 1;
return promise return promise
.then(() => { .then(() => {
let message; // There used to be a call to `this.notifs.add(message)` here, but now
if (numTasks == 1) { // that task status changes are logged in the notifications anyway,
message = `Task ${description}`; // it's no longer necessary.
} else { // This function is still kept, in case we want to bring back the
message = `${numTasks} tasks ${description}`; // notifications when multiple tasks can be selected. Then a summary
} // ("N tasks requeued") could be logged here.
this.notifs.add(message);
}) })
.catch((error) => { .catch((error) => {
const errorMsg = JSON.stringify(error); // TODO: handle API errors better. const errorMsg = JSON.stringify(error); // TODO: handle API errors better.