Struct MetadataChangesParams 

pub struct MetadataChangesParams {
    pub filter_related_type: Option<String>,
    pub filter_metadata_type: Option<Vec<String>>,
    pub extra: Map<String, Value>,
}

Extra method-level arguments for Metadata/changes (draft-ietf-jmap-metadata-01 §3.3).

Both filter fields are optional. Pass None (or Default::default()) to fetch all Metadata changes regardless of relatedType or @type.

Per §3.3, when both filters are specified the server MUST return only changes to Metadata objects that satisfy both criteria (logical AND). The state token returned in the response represents the complete account state and is independent of the filters; clients that use these filters MUST re-use the same filter values across subsequent Metadata/changes calls to ensure consistent synchronisation.

Fields

filter_related_type: Option<String>

Restrict the created/updated/destroyed arrays in the response to Metadata objects whose relatedType equals this value (draft-ietf-jmap-metadata-01 §3.3).

filter_metadata_type: Option<Vec<String>>

Restrict the created/updated/destroyed arrays in the response to Metadata objects whose @type is in this list (draft-ietf-jmap-metadata-01 §3.3).

None disables filtering on @type (all types are returned). Some(vec![]) is a legal empty array meaning “match no @type values” per draft §3.3 — the server returns empty created / updated / destroyed arrays regardless of actual changes. If you mean “return everything”, use None, not Some(vec![]).

extra: Map<String, Value>

Catch-all for vendor / site / private extension fields not covered by the typed fields above. Preserves unknown fields across deserialize/serialize round-trip per workspace extras-preservation policy (see workspace AGENTS.md).

Constraint: keys in extra MUST NOT collide with the typed-field wire names above (the camelCase spelling — e.g. "accountId", "ids", "properties", "blobIds", "fromAccountId", etc.). On collision the typed-field value wins on the wire and the extra value is silently dropped at serialization. Place vendor extensions under vendor-prefixed keys (e.g. "acmeCorpFoo") to avoid the collision class.

Keys MUST NOT collide with the standard RFC 8620 §5.2 / draft-01 §3.3 arg names (accountId, sinceState, maxChanges, filterRelatedType, filterMetadataType); metadata_changes will silently retain the typed-field value if an extras key collides.

Trait Implementations

impl Clone for MetadataChangesParams

fn clone(&self) -> Self

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for MetadataChangesParams

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for MetadataChangesParams

fn default() -> Self

Returns the “default value” for a type.

impl Serialize for MetadataChangesParams

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.