Skip to content

Remove another sessionId usage#277295

Merged
mjbvz merged 1 commit intomicrosoft:mainfrom
mjbvz:dev/mjbvz/established-felidae
Nov 14, 2025
Merged

Remove another sessionId usage#277295
mjbvz merged 1 commit intomicrosoft:mainfrom
mjbvz:dev/mjbvz/established-felidae

Conversation

@mjbvz
Copy link
Collaborator

@mjbvz mjbvz commented Nov 13, 2025

For #274403

Copilot AI review requested due to automatic review settings November 13, 2025 23:28
@mjbvz mjbvz enabled auto-merge November 13, 2025 23:28
@vs-code-engineering
Copy link

📬 CODENOTIFY

The following users are being notified based on files changed in this PR:

@bpasero

Matched files:

  • src/vs/workbench/contrib/chat/browser/chatInputPart.ts

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR continues the migration from sessionId (string-based) to sessionResource (URI-based) identifiers in the chat feature, addressing issue #274403. The changes deprecate the sessionId property in the IChatAgentRequest interface and update the ChatInputPart component to use URI-based session tracking.

  • Deprecates sessionId in IChatAgentRequest interface with proper JSDoc annotation
  • Migrates _lastEditingSessionId to _lastEditingSessionResource in ChatInputPart
  • Updates session comparison logic from string equality to URI equality using isEqual()

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
src/vs/workbench/contrib/chat/common/chatAgents.ts Adds deprecation comment to sessionId property, directing developers to use sessionResource instead
src/vs/workbench/contrib/chat/browser/chatInputPart.ts Refactors tracking of editing sessions from string-based IDs to URI-based resources, including variable rename and proper URI comparison

@mjbvz mjbvz merged commit 69c2a2c into microsoft:main Nov 14, 2025
22 of 23 checks passed
@vs-code-engineering vs-code-engineering bot locked and limited conversation to collaborators Dec 29, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants