Skip to content

fix: Start Over button now properly resets state to allow new generations #65

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.

Sign up for GitHub

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

Open
aj47 wants to merge 6 commits into
base: main
Choose a base branch
from
Open

fix: Start Over button now properly resets state to allow new generations #65

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
89186f8
fix: Start Over button now properly resets state to allow new generat…
aj47 Dec 15, 2025
e56b852
fix: add cancellation mechanism for in-flight requests on Start Over
aj47 Dec 15, 2025
7554da9
fix: guard setLoading in finally block to prevent race condition
aj47 Dec 15, 2025
3529178
fix: Reset refinement state and close history browser on Start Over
aj47 Dec 15, 2025
e16c34f
fix: use duck typing for AbortError check to handle DOMException in a…
aj47 Dec 15, 2025
8e58537
fix: abort in-flight requests on component unmount
aj47 Dec 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion app/thumbnails/page.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -849,6 +849,17 @@ export default function Home() {
setBlobUrls([]);
};

// Start over: clear results and go back to step 1
const handleStartOver = () => {
cleanupBlobUrls();
Copy link

@augmentcode augmentcode bot Dec 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If “Start Over” can be clicked while generation or suggested-refinement fetches are still in flight, those async completions can still update results/suggestedRefinements (index-keyed) after this reset, potentially causing stale suggestions or a stuck loading state. Consider adding a guard/cancellation mechanism for outstanding async work when starting over.

🤖 Was this useful? React with 👍 or 👎

setResults([]);
setLabeledResults([]);
setSuggestedRefinements({});
setLoadingSuggestions({});
setError(null);
goTo(1);
Copy link

@augmentcode augmentcode bot Dec 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

handleStartOver clears generation state but doesn’t reset refinementState (e.g., isRefinementMode) or close related UI like the history browser. If a user clicks Start Over while refining, this can leave the app “stuck” in refinement mode and also prevent suggested refinements from being fetched on the next run due to the !refinementState.isRefinementMode guard.

🤖 Was this useful? React with 👍 or 👎

};

const generate = async () => {
// Get all valid template IDs (custom + curated)
const allValidTemplateIds = new Set([
Expand Down Expand Up @@ -2125,7 +2136,7 @@ export default function Home() {

{/* Compact nav */}
<div className={styles.navRow} style={{ marginTop: 12 }}>
<button onClick={() => goTo(1)} style={{ padding: '6px 12px', fontSize: 13 }}>← Start Over</button>
<button onClick={handleStartOver} style={{ padding: '6px 12px', fontSize: 13 }}>← Start Over</button>
</div>
</>
)}
Expand Down