grishka/lemmy
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

300 comment limit. (#3306)

Browse source 
* 300 comment limit.

* Another fix.
This commit is contained in:
Dessalines 2023-07-03 18:02:57 -04:00 committed by GitHub
parent 7a04971ecd
commit f0e487f18a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 6 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
crates/api_common/src/utils.rs
View file

@ -670,7 +670,6 @@ pub async fn remove_user_data_in_community(
.pool(pool) .pool(pool)
.creator_id(Some(banned_person_id)) .creator_id(Some(banned_person_id))
.community_id(Some(community_id)) .community_id(Some(community_id))
.limit(Some(i64::MAX))
.build() .build()
.list() .list()
.await?; .await?;

9
crates/db_views/src/comment_view.rs
View file

@ -36,7 +36,7 @@ use lemmy_db_schema::{
post::Post, post::Post,
}, },
traits::JoinView, traits::JoinView,
utils::{fuzzy_search, get_conn, limit_and_offset_unlimited, DbPool}, utils::{fuzzy_search, get_conn, limit_and_offset, DbPool},
CommentSortType, CommentSortType,
ListingType, ListingType,
}; };
@ -340,9 +340,12 @@ impl<'a> CommentQuery<'a> {
// This does not work for comment trees, and the limit should be manually set to a high number // This does not work for comment trees, and the limit should be manually set to a high number
// //
// If a max depth is given, then you know its a tree fetch, and limits should be ignored // If a max depth is given, then you know its a tree fetch, and limits should be ignored
(i64::MAX, 0) // TODO a kludge to prevent attacks. Limit comments to 300 for now.
// (i64::MAX, 0)
(300, 0)
} else { } else {
limit_and_offset_unlimited(self.page, self.limit) // limit_and_offset_unlimited(self.page, self.limit)
limit_and_offset(self.page, self.limit)?
}; };
query = match self.sort.unwrap_or(CommentSortType::Hot) { query = match self.sort.unwrap_or(CommentSortType::Hot) {