fix: Advertise m.forget_forced_upon_leave capability according to config

This commit is contained in:
Bardi Harborow authored and Ellis Git committed 2026-11-04 18:48:40 +00:00
1 parent 34c5787af0
commit dad9e1426c
2 files changed
+3 -1

No files matched your search

+1
View File
@@ -0,0 +1 @@
The `m.forget_forced_upon_leave` capability now reflects the `forget_forced_upon_leave` config option instead of always being advertised as enabled.
+2 -1
View File
@@ -46,7 +46,8 @@ pub(crate) async fn get_capabilities_route(
capabilities.get_login_token =
GetLoginTokenCapability::new(services.server.config.login_via_existing_session);
capabilities.forget_forced_upon_leave.enabled = true;
capabilities.forget_forced_upon_leave.enabled =
services.server.config.forget_forced_upon_leave;
if services.users.is_admin(sender_user).await {
capabilities.account_moderation.lock = true;