Queue back-to-back shots instead of superseding (/skip, /fix <id>) - #44
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes the gap reported on Discord: pulling a second shot before answering the first questionnaire used to supersede the first one — it was saved with whatever was answered (or skipped outright) and there was no way to go back and rate it.
Now
/skipdrops the questionnaire in progress and moves on to the next queued shot (partial answers are still saved)./fix <id>(e.g./fix 62) reopens any shot from the machine index — the explicit "go back and rate that one" door. It jumps the queue: the questionnaire in progress is parked with its answers intact and resumes afterwards./fixwithout an id still redoes the last shot.Tests cover queue order, skip, restart persistence and queue-jumping. Version bumped to 0.4.0.