.NET: docs: clarify chat client pipeline order as outer to inner#6496
Open
iangithub wants to merge 1 commit into
Open
.NET: docs: clarify chat client pipeline order as outer to inner#6496iangithub wants to merge 1 commit into
iangithub wants to merge 1 commit into
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates API documentation to clarify the order of components in the harness agent’s chat client pipeline.
Changes:
- Corrected the described chat client pipeline direction from “inner to outer” to “outer to inner”.
| /// </para> | ||
| /// <para> | ||
| /// <strong>Chat client pipeline (inner to outer):</strong> | ||
| /// <strong>Chat client pipeline (outer to inner):</strong> |
github-actions
Bot
changed the title
This file contains hidden or 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
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.
Motivation and Context
This change clarifies the wording used to describe the chat client pipeline order.
No open issue is linked.
Description
The previous wording could be interpreted as listing the pipeline from inner to outer, which may cause readers to misunderstand the actual registration and wrapping behavior. The updated wording makes the intended order explicit and helps users understand how handlers are composed in the chat client pipeline.
This contributes to documentation accuracy and helps developers reason about request and response flow when configuring chat client pipeline handlers.
Contribution Checklist