Skip to content

fix(vscode): fix pipeline test and lint failures - #13534

Merged
marius-kilocode merged 1 commit into
mainfrom
fix-pipeline-issues
Aug 28, 2026
Merged

fix(vscode): fix pipeline test and lint failures#13534
marius-kilocode merged 1 commit into
mainfrom
fix-pipeline-issues

Conversation

@marius-kilocode

@marius-kilocode marius-kilocode commented Aug 28, 2026

Copy link
Copy Markdown
Collaborator

What Problem This Solves

The VS Code pipeline failed because a Happy DOM fixture did not expose IntersectionObserver, and the session context exceeded the enforced ESLint file-size limit.

Why This Change Was Made

The activity fixture now exposes the browser API used by the mounted UI. The session context value type is moved to a dedicated type module, and the source contract test follows the type declaration.

User Impact

No production behavior changes. The VS Code unit-test and production build checks can complete successfully.

Evidence

  • Full VS Code unit suite: 4,405 passed
  • Production build check: passed
  • ESLint: passed
  • Webview typecheck: passed
  • Prettier, Knip, and marker checks: passed

@kilo-code-bot

kilo-code-bot Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (4 files)
  • packages/kilo-vscode/tests/fixtures/session-provider-activity.tsx
  • packages/kilo-vscode/tests/unit/prompt-send-contract.test.ts
  • packages/kilo-vscode/webview-ui/src/context/session-types.ts
  • packages/kilo-vscode/webview-ui/src/context/session.tsx

Reviewed by grok-4.6 · Input: 60K · Output: 6.5K · Cached: 308.5K

Review guidance: REVIEW.md from base branch main

@marius-kilocode
marius-kilocode merged commit 142db49 into main Aug 28, 2026
23 checks passed
@marius-kilocode
marius-kilocode deleted the fix-pipeline-issues branch August 28, 2026 09:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants