We need to decide what to do about data processors, so I've collected some related issues here in this meta.
In summary, in D8+ we only use data processor plugins for token replacement in direct input mode in the UI. There is currently no way to use any data processor plugin other than 'rules_tokens', and 'rules_tokens' is always used - there's no provision for conditional use of the processor.
Moreover, if we want token replacement with programmatically-created rules, we have to ->process()
the rule explicitly. Is this desirable? Or should the processors be uniformly applied to both UI-created rules and programmatically-created rules?
Most things (all things?) that were done in D7 using data processors can now be done with DataFilter plugins in the typed_data module. Here's a list of things @fago has said in the related issues (notes/clarifications in parentheses were added by me).
{{ date|dateOffset('+1day') }}
. So auto-attaching them + make them (tagged) services seems to be the most reasonableActive
4.0
Rules Core
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.