You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did not expect it. I thought maybe I could look at several examples of tasks and then go back to the main page and accept the first one that I previewed.
If this is the desired behavior, I can document that on the help page.
Poster: Cash Costello id: 248
The text was updated successfully, but these errors were encountered:
The preview skip code uses the same session variable to maintain the skips:
defskip_task(request, batch_id, task_id):
""" Skip to next task when previewing a task """_add_task_id_to_skip_session(request.session, batch_id, task_id)
returnredirect(preview_next_task, batch_id)
We would have to separate preview_next_task() from the _skip_aware_next_available_task_id() function. It could instead be replaced by a function that gets the next task after the one specified.
I did not expect it. I thought maybe I could look at several examples of tasks and then go back to the main page and accept the first one that I previewed.
If this is the desired behavior, I can document that on the help page.
Poster: Cash Costello id: 248
The text was updated successfully, but these errors were encountered: