jmug/stoatchat
1
0
Fork 1
Code Issues Packages Projects Releases Wiki Activity

fix: ensure limit is always at least 1 when sent to database

Browse Source
This commit is contained in:
Paul Makles
2025-02-10 17:51:22 +00:00
parent e957af4ca3
commit 5f84daa9db
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
crates/core/database/src/models/messages/ops/mongodb.rs
View File

@@ -95,7 +95,7 @@ impl AbstractMessages for MongoDb {
COL, COL,
older_message_filter, older_message_filter,
FindOptions::builder() FindOptions::builder()
.limit(limit / 2) .limit(limit / 2 + 1)
.sort(doc! { .sort(doc! {
"_id": -1_i32 "_id": -1_i32
}) })

2
crates/core/models/src/v0/messages.rs
View File

@@ -280,7 +280,7 @@ auto_derived!(
pub struct OptionsQueryMessages { pub struct OptionsQueryMessages {
/// Maximum number of messages to fetch /// Maximum number of messages to fetch
/// ///
/// For fetching nearby messages, this is \`(limit + 1)\`. /// For fetching nearby messages, this is \`(limit + 2)\`.
#[cfg_attr(feature = "validator", validate(range(min = 1, max = 100)))] #[cfg_attr(feature = "validator", validate(range(min = 1, max = 100)))]
pub limit: Option<i64>, pub limit: Option<i64>,
/// Message id before which messages should be fetched /// Message id before which messages should be fetched