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

Allow ChatCompletionOption properties to be set/changed after instantiation #76

Conversation

RogerBarreto
Copy link
Contributor

The same way we can change Tools and other Properties in the Options class for long running Chats we normally need to change the ToolChoice, and as well as other properties of the chat iteration.

Currently that is only possible allocating (deep cloning) a new Option instance with those few options with the desired value.

@trrwilson
Copy link
Collaborator

Thanks for this, @RogerBarreto -- as mentioned on the pinged issue, we agree with this need and we're going to make the change across all top-level request option types like this; there's really no good reason for request option properties to be treated like client option properties.

We have to make a small change to the generated layer to catch everything (hence why it's not just done yet) but it won't be a long wait.

@joseharriaga
Copy link
Collaborator

The change replacing uses of init for set has been published as part of NuGet package version 2.0.0-beta.8:
🔗 https://www.nuget.org/packages/OpenAI/2.0.0-beta.8

I think we can close this PR now. 😊

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.

3 participants