-
Notifications
You must be signed in to change notification settings - Fork 384
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
Missing name
parameter in chat completion message parameters.
#118
Comments
cc @nknj – thoughts on adding this? |
@rattrayalex @nknj any more information on this? I encountered this issue when migrating from version 3.x.x and it seems like these parameters are not deprecated. |
It looks like they're deprecating |
Can you confirm what the issue is? We document these in the API, are you saying they are not supported here in the SDK? |
Yes, they are not supported in the SDK - types I am using the node library v4.18.0. |
This should be fixed soon! Hang tight. |
@logankilpatrick any info on this? |
Fixed! |
@logankilpatrick @rattrayalex I updated the npm package version to the current latest version (v4.20.1) and the |
Same (?) issue here. I'm using
My payload looks like this:
|
Sorry about this! A true fix has merged on this repo and should go out in the SDKs shortly. |
Still seems to be broken? |
@shamoons where do you see |
According to the documentation we should be able to specify the name for each of the base message types/roles (system, assistant, and user) to provide the model with additional information to differentiate between participants of the same role (useful for few-shot prompting).
The text was updated successfully, but these errors were encountered: