JMAP: an unknown capability is unknownCapability, not notRequest #210

Merged

jcoffey-dev merged 1 commits from fix/unknown-capability into main

2026-10-26 16:01:49 +00:00

Author	SHA1	Message	Date
jcoffey-dev	f95c64c698	JMAP: an unknown capability in "using" is unknownCapability ci / fork-checks (pull_request) Skipped Details ci / build (pull_request) Skipped Details github/ci (branch) GitHub Actions Details ci / github (pull_request) Successful in 20m26s Details A request naming a capability the server doesn't offer failed as a whole parse error, so the client got notRequest with serde's message. RFC 8620 section 3.6.1 says unknownCapability, and a client that checks for it can tell the user what's wrong (an old capability name, a feature this server doesn't have). "using" now parses without failing and keeps the first unknown name; Request::parse and WebSocketMessage::parse then fail with JmapEvent::UnknownCapability, which already maps to the error type, with the name as its detail.	2026-10-26 08:40:59 -07:00

Author

SHA1

Message

Date

jcoffey-dev

f95c64c698

JMAP: an unknown capability in "using" is unknownCapability

ci / fork-checks (pull_request) Skipped

Details

ci / build (pull_request) Skipped

Details

github/ci (branch) GitHub Actions

Details

ci / github (pull_request) Successful in 20m26s

Details

A request naming a capability the server doesn't offer failed as a whole
parse error, so the client got notRequest with serde's message. RFC 8620
section 3.6.1 says unknownCapability, and a client that checks for it can
tell the user what's wrong (an old capability name, a feature this server
doesn't have).

"using" now parses without failing and keeps the first unknown name;
Request::parse and WebSocketMessage::parse then fail with
JmapEvent::UnknownCapability, which already maps to the error type, with
the name as its detail.

2026-10-26 08:40:59 -07:00