The result of this should allow the filter definition’s `self`’s class can be customized (for more targeted conditions and such).
Allow defining multible conditions, actions in the filter body. Then at the end of the block finalize into filter object & register that.
This would make it much easier to reason about / test filter negation & stuff like archive_unless_directed.
Something like this?
has :to, '[email protected]'
has :from, '[email protected]'
Might also make it easier to optimize filter expressions for length (but how to specify OR? Guess this is for a version 1.0/2.0)
While it’s neat that I can keep them in here, I should just make a separate repo for them.