inbuxa/inbuxa-server
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 23 Wiki Activity

Principal get test: expect legacyAllowed
ci / fork-checks (pull_request) Successful in 12s
Details
ci / build (pull_request) Successful in 1h18m28s
Details

Browse Source 
The per-protocol switches (#79) added legacyAllowed to the account's
urn:inbuxa:jmap capability, but this expectation wasn't updated, so
jmap_tests stopped here and the suites after it never ran.
This commit is contained in:
jcoffey-dev
2026-09-28 06:42:08 -07:00
parent b2453d066b
commit eac3db34e9
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/src/jmap/principal/get.rs
+1 -1
View File
@@ -254,7 +254,7 @@ pub async fn test(test: &TestServer) {
// inbuxa: MT-22, the logo that applies to the account, and // inbuxa: MT-22, the logo that applies to the account, and
// LP-19, whether the legacy protocols are open to it, and // LP-19, whether the legacy protocols are open to it, and
// ai-explain EX-1, whether Explain can be offered // ai-explain EX-1, whether Explain can be offered
"urn:inbuxa:jmap": { "logo": null, "legacyProtocols": "enabled", "aiExplain": false }, "urn:inbuxa:jmap": { "logo": null, "legacyProtocols": "enabled", "legacyAllowed": ["imap", "pop3", "manageSieve", "submission"], "aiExplain": false },
"https://www.fastmail.com/dev/maskedemail": {} "https://www.fastmail.com/dev/maskedemail": {}
} }
} }