fix: metadata deserialization/type issue in GetResult struct

[ishaksebsib]

This PR fixes Incorrect Metadata Deserialization in Rust Client (GetResult Struct) #24.

Issue:

The GetResult struct expected:

pub metadatas: Option<Vec<Option<Vec<Option<Metadata>>>>>,

But the API returns:

pub metadatas: Option<Vec<Option<Metadata>>>,

This mismatch caused a deserialization error:

error decoding response body: invalid type: map, expected a sequence at line 1 column 3571

Fix:

• Changed metadatas type in GetResult to correctly match the API response.
• Added test case test_get_all_metadatas_from_collection to verify fetching metadata from a collection.

Example from Chroma Docs:

metadatas: [{ "key": "value" }, { "key": "value" }]

Result:

With this fix, the Rust client now correctly deserializes metadata, allowing users to get collection data along with metadata without encountering errors.

Example Usage:

Here’s how to fetch collection data with metadata:

let get_query = GetOptions {
    ids: vec![],
    where_metadata: None,
    limit: None,
    offset: None,
    where_document: None,
    include: Some(vec!["metadatas".into()]),
};

let get_result = collection.get(get_query).await.unwrap();

This example shows how to get data from a collection, including metadata, without any deserialization issues.

[Anush008]

Thank you @ishaksebsib. LGTM!

[github-actions]

🎉 This PR is included in version 2.2.2 🎉

The release is available on:

• GitHub release
• v2.2.2

Your semantic-release bot 📦🚀