#[non_exhaustive]pub struct MetadataTextMatch {
pub path: String,
pub value: String,
}Expand description
Value shape for the text-matching metadata filter conditions (draft-ietf-jmap-metadata-04 §3.6).
Used as the value of the metadataTextContains,
privateMetadataTextContains, metadataTextEquals, and
privateMetadataTextEquals fields on per-type FilterCondition objects.
§Wire example (from §6.7)
{
"path": "acme.example.com/memo",
"value": "follow up"
}§Path syntax
draft-ietf-jmap-metadata-04 §3.6: the path is “a namespace
identifier, optionally followed by a JSON Pointer [RFC6901] into the
namespace value (for example, <namespace>, <namespace>/<key> or
<namespace>/<key>/<subkey>)”. / and ~ inside a key are escaped as
~1 and ~0 per RFC 6901.
Object members are addressed by name; a path that would traverse an
array or a scalar addresses no value. A server rejects a path with an
invalid ~ escape with invalidArguments. Same syntax as the string
value of metadataExists.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.path: StringPath within the metadata object to match against.
Form: <namespace>, optionally followed by an RFC 6901 JSON
Pointer into the namespace value, such as <namespace>/<key> or
<namespace>/<key>/<subkey>.
value: StringThe string to search for at path. Interpretation (substring
containment vs exact equality) depends on which filter condition
field carries this MetadataTextMatch.