[FIX] N+1 API Call: Missing bulk archive capability#522
Conversation
Co-authored-by: n24q02m <135627235+n24q02m@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
- Implemented bulk archive in `background.js` using `archiveTasks` and batching (50 tasks/batch). - Updated Biome configuration in `biome.json` to v2.5.1 and fixed deprecated fields. - Resolved accessibility lint errors in `popup.html` using semantic `<fieldset>` and `<legend>`. - Updated tests in `tests/perf.test.js` and `tests/background.test.js` to support bulk operations. - Verified changes with 234 passing tests and Playwright visual verification. Co-authored-by: n24q02m <135627235+n24q02m@users.noreply.github.com>
The
archiveTaskfunction was modified to accept an array of task IDs, renaming it toarchiveTasks. TheexecuteArchiveloop was refactored to chunk tasks into batches of 50 (defined byARCHIVE_BATCH_SIZE) and process them in bulk. This reduces the number of API calls significantly. Tests were updated to verify the new batching behavior.PR created automatically by Jules for task 4016319747220684838 started by @n24q02m