At the moment DenyThenTry<(),(.....)> would always deny with the empty tuple because it returns Err() on nothing matched.
Keith mentioned that returning NoRulesMatched from RejectReason that https://github.com/paritytech/polkadot/pull/5035/ is introducing might help. It might be clearer if we had an opposite of the ShouldExecute trait.
We currently have a set of allow rules that will let certain messages through using the
ShouldExecute
tuple.The suggestion is to have a guard that ensures that any matching message is denied:
At the moment
DenyThenTry<(),(.....)>
would always deny with the empty tuple because it returns Err() on nothing matched.Keith mentioned that returning
NoRulesMatched
fromRejectReason
that https://github.com/paritytech/polkadot/pull/5035/ is introducing might help. It might be clearer if we had an opposite of theShouldExecute
trait.