Skip to content

Non-positive

nonPositive validates that a number is less than or equal to zero.

It enforces strict numeric validation and rejects any non-number value, NaN, or positive numbers. If the value is not a number or is positive, the rule emits a single validation event. Otherwise, it produces no validation output.

Signature

Through the API:

.nonPositive()

And internally:

export const nonPositive: ValidationRule
(value: unknown, path: FieldPath) => Promise<ReadonlyArray<JaneEvent>>

Events

Event code Description
type.not.valid Value is not structurally a number or is NaN
number.not.non-positive Number is greater than zero

Design rationale

  • Provides a strict, predictable non-positive number validation.
  • Accepts zero and negative values.
  • Rejects non-number values with a clear structural-type diagnostic.
  • Never coerces or normalizes — validation is explicit and opt-in.
  • Emits exactly one event per failure for clarity and composability.
  • Async-compatible and returns a readonly array of JaneEvent objects.

Invoke

nonPositive runs only when explicitly included in a boundary or pipeline. It does not run automatically.

The rule activates when:

  • The value is any JavaScript value.
  • If the value is not a number or is NaN, emits type.not.valid.
  • If the value is a number but greater than zero, emits number.not.non-positive.
  • If the value is zero or negative → returns an empty result set.

Examples

Valid non-positive number

await nonPositive(-5, "$");
// → []

Valid zero

await nonPositive(0, "$");
// → []

Positive number

await nonPositive(5, "$");
// → [
//     JaneEvent{
//       kind: "error",
//       code: "number.not.non-positive",
//       path: "$",
//       ...
//     }
//   ]

Non-number value

await nonPositive("-5", "$");
// → [
//     JaneEvent{
//       kind: "error",
//       code: "type.not.valid",
//       path: "$",
//       ...
//     }
//   ]