Ordering of ensure / ensureOr arguments in MonadError

Apologies if this has already been raised; I couldn't find any related Issues / PRs.

I'm just wondering what the reasoning is for the ordering of the arguments of MonadError#ensure and MonadError#ensureOr.

I think typical usage of them leads to code that reads confusingly e.g.

case object CustomerUnderage extends Exception
def isCustomerOfLegalAge(customer: Customer): Boolean = ???

// F has MonadError type class
val customer: F[Customer] = ???

// current API - reads confusingly i.e. ensure customer is underage ?!
customer.ensure(CustomerUnderage)(isCustomerOfLegalAge)

Instead, what are peoples' thoughts on something like:

// proposed API
customer.ensure(isCustomerOfLegalAge)(onError = CustomerUnderage)

Start by reading the MonadError#ensure and MonadError#ensureOr entry points and compare their current argument ordering with the proposed calls in this issue. Done means reaching a maintainer-backed decision on whether the API should change; the issue does not identify implementation files or tests.