Skip to content

Fix incompatibility with API requirements #252

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

Merged
merged 1 commit into from
Aug 29, 2024
Merged

Conversation

vrurg
Copy link
Contributor

@vrurg vrurg commented Jul 30, 2024

For CreateAssistantToolFileSearchResources struct the API expects only one of the two fields to be used. Even an empty array is not accepted if the other field contains a value. Thus making both vector_store_ids and vector_stores optional is the way to go.

Fixes #251

For `CreateAssistantToolFileSearchResources` struct the API expects
only one of the two fields to be used. Even an empty array is not
accepted if the other field contains a value. Thus making both
`vector_store_ids` and `vector_stores` optional is the way to go.

Fixes 64bit#251
@vrurg
Copy link
Contributor Author

vrurg commented Jul 30, 2024

Luckily, this fix is very simple. :)

Copy link

@human-d3v human-d3v left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When I changed this locally, it fixed the API requirement issue.

Copy link
Owner

@64bit 64bit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the PR!

@64bit 64bit merged commit 650281d into 64bit:main Aug 29, 2024
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.

CreateAssistantToolResources fields must be optional?
3 participants