Fix handling of text-only user messages in AzureAIInferenceChatClient #5714
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.
ChatRequestUserMessage
has three constructors:but even though all of the parameters are named
content
and represent the message's content, they behave differently. The first assigns the string content to the instance'sContent
property and leaves itsMultimodalContentItems
property null, and the others leaveContent
null and setMultimodalContentItems
to the property. For models that don't support multi-modal, using the latter two constructors breaks, even when the content is a single text item.I think this should be improved in Azure.AI.Inference, but regardless, this fixes the ToAzureAIInferenceChatMessages helper to special-case text-only inputs and use the first
string
-based constructor rather than always using theIEnumerable<ChatMessageContentItem>
-based one.Fixes #5708
Microsoft Reviewers: Open in CodeFlow