From a64558b504870a5a3970308fd18c3c4714813c2a Mon Sep 17 00:00:00 2001 From: Hugh Nimmo-Smith Date: Mon, 13 Oct 2025 09:45:14 +0100 Subject: [PATCH] Make `soft_limit` optional for conciseness --- proposals/4335-user-limit-exceeded.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/proposals/4335-user-limit-exceeded.md b/proposals/4335-user-limit-exceeded.md index 609bd2c91..f8460e643 100644 --- a/proposals/4335-user-limit-exceeded.md +++ b/proposals/4335-user-limit-exceeded.md @@ -34,8 +34,8 @@ The error response must also contain additional fields: * `info_uri` string (required) - an opaque URI that the client can link the user to in order to get more context on the error. -* `soft_limit` boolean (required) - `true` means that the specific limit encountered can be increased. `false` means - that it is a hard limit that cannot be increased. +* `soft_limit` boolean (optional, default `false`) - `true` means that the specific limit encountered can be increased. + Otherwise it is a hard limit that cannot be increased. * `increase_uri` (required if `soft_limit` is `true`) - an opaque URI where the user can undertake actions to increase the encountered limit. @@ -63,8 +63,7 @@ For a hard limit: { "errcode": "M_USER_LIMIT_EXCEEDED", "error": "User has exceeded their storage quota of 10GB", - "info_uri": "https://example.com/homeserver/about?limit_type=quota", - "soft_limit": false + "info_uri": "https://example.com/homeserver/about?limit_type=quota" } ```