Rename IChatClient members and corresponding types#5870
Rename IChatClient members and corresponding types#5870stephentoub merged 4 commits intodotnet:mainfrom
Conversation
🎉 Good job! The coverage increased 🎉
Full code coverage report: https://dev.azure.com/dnceng-public/public/_build/results?buildId=947185&view=codecoverage-tab |
After great feedback on usage of the APIs, re-reviewing the state of the ecosystem, and length discussions, we're renaming the members of IChatClient to destress the notion of "completions" and instead focus just on getting back a {streaming} response.
da2e0b4 to
4ae06da
Compare
🎉 Good job! The coverage increased 🎉
Full code coverage report: https://dev.azure.com/dnceng-public/public/_build/results?buildId=947770&view=codecoverage-tab |
Co-authored-by: Steve Sanderson <SteveSandersonMS@users.noreply.github.com>
…InferenceChatClient.cs Co-authored-by: Steve Sanderson <SteveSandersonMS@users.noreply.github.com>
🎉 Good job! The coverage increased 🎉
Full code coverage report: https://dev.azure.com/dnceng-public/public/_build/results?buildId=948177&view=codecoverage-tab |
🎉 Good job! The coverage increased 🎉
Full code coverage report: https://dev.azure.com/dnceng-public/public/_build/results?buildId=948307&view=codecoverage-tab |
After great feedback on usage of the APIs, re-reviewing the state of the ecosystem, and length discussions, we're renaming the members of IChatClient to destress the notion of "completions" and instead focus just on getting back a {streaming} response.
Closes #5868
Microsoft Reviewers: Open in CodeFlow