15 Commits (10c509425fb6e36cba63de94402a9a5772cba54c)

Author	SHA1	Message	Date
Patrick Cloke	f880e64b11	Stabilize support for MSC3952: Intentional mentions. (#15520)	1 year ago
Patrick Cloke	820f02b70b	Stabilize support for MSC3966: event_property_contains push condition. (#15187) ... This removes the configuration flag & updates the identifiers to use the stable version.	2 years ago
Patrick Cloke	fd9cadcf53	Stabilize support for MSC3758: event_property_is push condition (#15185) ... This removes the configuration flag & updates the identifiers to use the stable version.	2 years ago
Erik Johnston	242d2a27ce	Use nightly rustfmt in CI (#15188) ... As we use some nightly only options, e.g. to group and sort imports consistently.	2 years ago
Patrick Cloke	8ef324ea6f	Update intentional mentions (MSC3952) to depend on `exact_event_property_contains` (MSC3966). (#15051) ... This replaces the specific `is_user_mention` push rule condition used in MSC3952 with the generic `exact_event_property_contains` push rule condition from MSC3966.	2 years ago
Patrick Cloke	e746f80b4f	Do not accept pattern_type from user input in push rules. (#15088) ... Internally the push rules module uses a `pattern_type` property for `event_match` conditions (and `related_event_match`) to mark the condition as matching the current user's Matrix ID or localpart. This is leaky to the Client-Server API where a user can successfully set a condition which provides `pattern_type` instead of `pattern` (note that there's no benefit to doing this -- the user can just use their own Matrix ID or localpart instead). When serializing back to the client the `pattern_type` property is converted into a proper `pattern`. The following changes are made to avoid this: * Separate the `KnownCondition::EventMatch` enum value into `EventMatch` and `EventMatchType`, each with their own expected properties. (Note that a similar change is made for `RelatedEventMatch`.) * Make it such that the `pattern_type` variants serialize to the same condition kind, but cannot be deserialized (since they're only provided by base rules). * As a final tweak, convert `user_id` vs. `user_localpart` values into an enum.	2 years ago
Patrick Cloke	979f237b28	Update intentional mentions (MSC3952) to depend on `exact_event_match` (MSC3758). (#15037) ... This replaces the specific `is_room_mention` push rule condition used in MSC3952 with the generic `exact_event_match` push rule condition from MSC3758. No functionality changes due to this.	2 years ago
Patrick Cloke	119e0795a5	Implement MSC3966: Add a push rule condition to search for a value in an array. (#15045) ... The `exact_event_property_contains` condition can be used to search for a value inside of an array.	2 years ago
Patrick Cloke	14be78d492	Support for MSC3758: exact_event_match push condition (#14964) ... This specifies to search for an exact value match, instead of string globbing. It only works across non-compound JSON values (null, boolean, integer, and strings).	2 years ago
Patrick Cloke	b2d97bac09	Implement MSC3958: suppress notifications from edits (#14960) ... Co-authored-by: Brad Murray <brad@beeper.com> Co-authored-by: Nick Barrett <nick@beeper.com> Copy the suppress_edits push rule from Beeper to implement MSC3958. 9415a1284b/rust/src/push/base_rules.rs (L98-L114)	2 years ago
Patrick Cloke	52700a0bcf	Support the backwards compatibility features in MSC3952. (#14958) ... If the feature is enabled and the event has a `m.mentions` property, skip processing of the legacy mentions rules.	2 years ago
Patrick Cloke	585180594b	Fix running cargo bench & test in CI. (#14943)	2 years ago
Andrew Morgan	a7b54ca8d8	Implement MSC3930: polls push rules (#14787)	2 years ago
Erik Johnston	890e5f610e	Fix Rust lint CI (#14602)	2 years ago
Erik Johnston	ebd9e2dac6	Implement push rule evaluation in Rust. (#13838)	2 years ago