anyOf()

Multiple rules targeting the same field are ANDed by default. Wrap them in anyOf() when any one successful path should unlock the target.

Use eitherOf() when those OR paths need names and each path is itself a group of ANDed rules.

Signature

anyOf(ruleA, ruleB, ruleC)

All inner rules must target the same fields, or creation throws.

Example

anyOf(
  enabledWhen('submit', ({ password }) => !!password, {
    reason: 'Enter a password',
  }),
  enabledWhen('submit', (_values, conditions) => conditions.bypass === true, {
    reason: 'Bypass flag missing',
  }),
)

Either a password or a bypass flag unlocks submit. When both fail, all inner reasons are collected in reasons.

Looking for allOf?

There is no allOf() — it is the default. Multiple rules targeting the same field are ANDed together by the evaluator without any explicit combinator:

// These two rules are implicitly ANDed on 'submit'
enabledWhen('submit', ({ email }) => !!email, { reason: 'Enter an email' }),
enabledWhen('submit', ({ password }) => !!password, { reason: 'Enter a password' }),

Both must pass for submit to be enabled.

If you need AND groups composable inside OR logic — for example, “path A requires condition 1 AND condition 2, OR path B requires condition 3 AND condition 4” — use eitherOf(). Each branch in eitherOf is an AND group, and branches are ORed:

eitherOf('submitAuth', {
  sso:      [enabledWhen('submit', hasSsoDomain), enabledWhen('submit', hasSsoToken)],
  password: [enabledWhen('submit', hasEmail), enabledWhen('submit', hasPassword)],
})
// equivalent to: anyOf(allOf(hasSsoDomain, hasSsoToken), allOf(hasEmail, hasPassword))

See also

• Quick Start: anyOf — interactive demo
• eitherOf() — named OR branches built from rule groups
• enabledWhen() — the most common inner rule for anyOf