client-api: Mention that backslashes should be escaped in filter event_fields
According to MSC3980
This commit is contained in:
parent
ef374ea6b0
commit
c1a36a2047
@ -289,8 +289,8 @@ pub struct FilterDefinition {
|
|||||||
///
|
///
|
||||||
/// If this list is absent then all fields are included. The entries may include '.' characters
|
/// If this list is absent then all fields are included. The entries may include '.' characters
|
||||||
/// to indicate sub-fields. So ['content.body'] will include the 'body' field of the 'content'
|
/// to indicate sub-fields. So ['content.body'] will include the 'body' field of the 'content'
|
||||||
/// object. A literal '.' character in a field name may be escaped using a '\'. A server may
|
/// object. A literal '.' or '\' character in a field name may be escaped using a '\'. A server
|
||||||
/// include more fields than were requested.
|
/// may include more fields than were requested.
|
||||||
#[serde(skip_serializing_if = "Option::is_none")]
|
#[serde(skip_serializing_if = "Option::is_none")]
|
||||||
pub event_fields: Option<Vec<String>>,
|
pub event_fields: Option<Vec<String>>,
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user