fix(vscode): reset read notifications from settings - #11716
Conversation
| if (cached) { | ||
| const persisted = ctx.context?.globalState.get<string[]>(KEY, []) ?? [] | ||
| const dismissedIds = | ||
| persisted.length > 0 ? Array.from(new Set([...cached.dismissedIds, ...persisted])) : cached.dismissedIds |
There was a problem hiding this comment.
WARNING: Resetting while the extension is offline still republishes the cached dismissed IDs
resetReadNotifications() clears globalState, but this branch treats an empty persisted list as a signal to fall back to cached.dismissedIds. If the user clicks the new settings button before the client reconnects, notificationsLoaded goes back out with the old IDs, so the notifications stay hidden even though the success toast is shown. Letting an empty persisted list win here, or special-casing the reset path, would make the new action work offline as well.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (25 files)
Fix these issues in Kilo Cloud Reviewed by gpt-5.4-20260305 · Input: 79.4K · Output: 13.6K · Cached: 596.7K Review guidance: REVIEW.md from base branch |
…ications fix(vscode): reset read notifications from settings
What
kilo.dismissedNotificationIdsand refresh notifications without resetting other settings.Why
Users need a targeted way to make previously read notifications visible again without using the broader settings reset.
Validation
bun run formatfrompackages/kilo-vscode/bun run typecheckfrompackages/kilo-vscode/bun run lintfrompackages/kilo-vscode/bun test tests/unit/message-contract.test.ts tests/unit/i18n-keys.test.tsfrompackages/kilo-vscode/