Skip to content

Clarify chat client resolution behavior in docs#24721

Merged
EngincanV merged 1 commit intorel-10.1from
10.1-chatclient-fallback-docs
Jan 23, 2026
Merged

Clarify chat client resolution behavior in docs#24721
EngincanV merged 1 commit intorel-10.1from
10.1-chatclient-fallback-docs

Conversation

@enisn
Copy link
Member

@enisn enisn commented Jan 23, 2026

Updated documentation to specify that if a chat client is not configured for a workspace, the default workspace's chat client is returned, and null is only returned if neither is configured.

Update docs according to #24717

Checklist

  • I fully tested it as developer / designer and created unit / integration tests
  • I documented it (or no need to document or I will create a separate documentation issue)

Updated documentation to specify that if a chat client is not configured for a workspace, the default workspace's chat client is returned, and null is only returned if neither is configured.
@enisn enisn added this to the 10.1-final milestone Jan 23, 2026
@enisn enisn requested a review from EngincanV January 23, 2026 11:06
Copilot AI review requested due to automatic review settings January 23, 2026 11:06
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 updates the documentation for Microsoft.Extensions.AI integration to accurately reflect the fallback behavior for chat client resolution introduced in PR #24717. The documentation now clarifies that when a workspace-specific chat client is not configured, the system falls back to the default workspace's chat client, and null is only returned when both are not configured.

Changes:

  • Updated the chat client resolution behavior description to document the fallback mechanism to the default workspace

@EngincanV EngincanV merged commit 3d78e98 into rel-10.1 Jan 23, 2026
8 checks passed
@EngincanV EngincanV deleted the 10.1-chatclient-fallback-docs branch January 23, 2026 11:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants