backups/grapevine
1
0
Fork 0
mirror of https://gitlab.computer.surgery/matrix/grapevine.git synced 2025-12-18 08:11:24 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

don't automatically wrap in RumaResponse

Browse source 
This allows us to use the `ruma_route` convenience function even when we
need to add our own hacks into the responses, thus making us less
reliant on Ruma.
This commit is contained in:
Charles Hall 2024-05-18 18:31:36 -07:00
parent 87ac0e2a38
commit 230ebd3884
No known key found for this signature in database
GPG key ID: 7B8E0645816E07CF
35 changed files with 438 additions and 405 deletions
Download patch file Download diff file Expand all files Collapse all files

6
src/api/client_server/report.rs
View file

@ -4,14 +4,14 @@ use ruma::{
int,
};
use crate::{services, Error, Result, Ruma};
use crate::{services, Error, Result, Ruma, RumaResponse};
/// # `POST /_matrix/client/r0/rooms/{roomId}/report/{eventId}`
///
/// Reports an inappropriate event to homeserver admins
pub(crate) async fn report_event_route(
body: Ruma<report_content::v3::Request>,
) -> Result<report_content::v3::Response> {
) -> Result<RumaResponse<report_content::v3::Response>> {
let sender_user = body.sender_user.as_ref().expect("user is authenticated");
let Some(pdu) = services().rooms.timeline.get_pdu(&body.event_id)? else {
@ -91,5 +91,5 @@ pub(crate) async fn report_event_route(
),
));
Ok(report_content::v3::Response {})
Ok(RumaResponse(report_content::v3::Response {}))
}