Closed dangchinh25 closed 6 hours ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @glharper.
This is similar to https://github.com/Azure/azure-sdk-for-js/issues/26579. It is intentional to hide those properties because we believe they're not relevant to the experience of the SDK customers. Could you please share how do you intend to use object
and model
?
I think I'm in a similar scenario with issue https://github.com/Azure/azure-sdk-for-js/issues/26579 where we just want to do some logging/auditing on our end. I also want to point out that the deploymentId is not always the model name so we can't rely on that. I see that you also mentioned some workaround but I'm not sure that is the best way to do this when we already have this information ready on our end.
Seeing the same issue
Hi @dangchinh25 and @huytool157, we strongly recommend that you migrate to use the AzureOpenAI
client exported by the official OpenAI client library for JavaScript. Checkout the migration guide for how to do so while maintaining typing for Azure features.
Please let us know if you have any other questions!
Describe the bug ChatCompletions interface does not contain
model
andobject
attribute, but the actual received payload does have these values.The code I tried with:
To Reproduce Steps to reproduce the behavior:
Expected behavior Type definition and actual response object match each other.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.