fix: add ordering_key on release struct

RustyNova016 · Jan 9, 2025 · 5b2bdff · 5b2bdff
1 parent 7ff1707
commit 5b2bdff
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 1 deletion.
diff --git a/src/entity/relations.rs b/src/entity/relations.rs
@@ -56,6 +56,9 @@ pub struct Relation {
     pub direction: String,
     #[serde(rename = "type")]
     pub relation_type: String,
+
+    /// The order of the relationship
+    pub ordering_key: Option<u64>,
 }
 
 #[derive(Debug, Serialize, Deserialize, PartialEq, Clone)]

diff --git a/tests/async_tests/api/fetch.rs b/tests/async_tests/api/fetch.rs
@@ -122,7 +122,8 @@ async fn should_get_artist_relations_from_release() {
             type_id: "87e922ba-872e-418a-9f41-0a63aa3c30cc".to_string(),
             begin: None,
             direction: "backward".to_string(),
-            relation_type: "engineer".to_string()
+            relation_type: "engineer".to_string(),
+            ordering_key: None
         }]
     );
 }

diff --git a/tests/blocking_tests/api/fetch.rs b/tests/blocking_tests/api/fetch.rs
@@ -119,6 +119,7 @@ fn should_get_artist_relations_from_release() {
             begin: None,
             direction: "backward".to_string(),
             relation_type: "engineer".to_string()
+            ordering_key: None
         }]
     );
 }