Description
== What
Requesting arbitrary headers, in persed forms, for bodyparts...
== The spec
In addition, the client may request/send EmailBodyPart properties representing individual header fields, following the same syntax and semantics as for the Email object, e.g., header:Content-Type.
== Definition of done:
- Write integrationt ests for the following additional properties:
- [ ] `header:Content-Type`
- [ ] `header:Content-Type:all`
- [ ] `header:Content-Type:asText`
- [ ] `header:Content-Type:asText:all`
Other asXXX methods should be supported.
== Example
{ "using": [ "urn:ietf:params:jmap:core", "urn:ietf:params:jmap:mail"], "methodCalls": [[ "Email/get", { "accountId": "29883977c13473ae7cb7678ef767cbfbaffc8a44a6e463d971d23a65c1dc4af6", "ids": ["3647"], "properties": ["htmlBody"], "bodyProperties": ["partId", "header:ContentType:asText"] }, "c1"]] }
Will return:
{ "sessionState": "75128aab4b1b", "methodResponses": [[ "Email/get", { "accountId": "29883977c13473ae7cb7678ef767cbfbaffc8a44a6e463d971d23a65c1dc4af6", "state": "000001", "list": [ { "id": "3647", "htmlBody": [ { "partId": "partId3", "header:ContentType:asText": "text/plain; charset=UTF-8", } ] ], "notFound": [] }, "c1"]] }
Attachments
Issue Links
- links to