Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[C#] chore: make assistants planner experimental #910

Merged
merged 3 commits into from
Nov 28, 2023

Conversation

singhk97
Copy link
Collaborator

Linked issues

closes: #905

Details

Change assistant planner related class' namespace from Microsoft.Teams.AI.AI.Planners to Microsoft.Teams.AI.AI.Planners.Experimental

Attestation Checklist

  • My code follows the style guidelines of this project

  • I have checked for/fixed spelling, linting, and other errors

  • I have commented my code for clarity

  • I have made corresponding changes to the documentation (we use TypeDoc to document our code)

  • My changes generate no new warnings

  • I have added tests that validates my changes, and provides sufficient test coverage. I have tested with:

    • Local testing
    • E2E testing in Teams
  • New and existing unit tests pass locally with my changes

@singhk97 singhk97 merged commit 82c1b65 into breaking-changes-2 Nov 28, 2023
5 checks passed
@singhk97 singhk97 deleted the kavin/assistants-planner-dotnet branch November 28, 2023 21:46
singhk97 added a commit that referenced this pull request Dec 6, 2023
## Linked issues

closes: #905 

## Details

Change assistant planner related class' namespace from
`Microsoft.Teams.AI.AI.Planners` to
`Microsoft.Teams.AI.AI.Planners.Experimental`

## Attestation Checklist

- [x] My code follows the style guidelines of this project

- I have checked for/fixed spelling, linting, and other errors
- I have commented my code for clarity
- I have made corresponding changes to the documentation (we use
[TypeDoc](https://typedoc.org/) to document our code)
- My changes generate no new warnings
- I have added tests that validates my changes, and provides sufficient
test coverage. I have tested with:
  - Local testing
  - E2E testing in Teams
- New and existing unit tests pass locally with my changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants