VSCODE-640: Adapt message content access to latest vscode API #857
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alenakhineika
approved these changes
Oct 24, 2024
nirinchev
added a commit
that referenced
this pull request
Oct 24, 2024
* main: VSCODE-640: Adapt message content access to latest vscode API (#857) Update changelog (#856)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
microsoft/vscode#231788 changes the content field type of LanguageModelChatMessage. This means that in insiders builds, we're seeing exceptions/test failures due to us assuming the content will always be a string. Since the type definitions haven't been updated to account for this breaking change, this PR takes a somewhat hacky approach of casting the content to
anyand then testing for string or array.Checklist
Motivation and Context
Types of changes