No lead space¶
noLeadSpace validates that a string does not begin with whitespace.
It enforces strict structural string validation and rejects any non-string value or string that starts with whitespace. If the value is not a string or starts with whitespace, the rule emits a single validation event. Otherwise, it produces no validation output.
Signature¶
Through the API:
.noLeadSpace()
And internally:
export const noLeadSpace: ValidationRule
(value: unknown, path: FieldPath) => Promise<ReadonlyArray<JaneEvent>>
Events¶
| Event code | Description |
|---|---|
type.not.valid |
Value is not structurally a string |
string.has.leading-whitespace |
String begins with whitespace |
Design rationale¶
- Provides a strict, predictable leading whitespace validation.
- Rejects non-string 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
JaneEventobjects.
Invoke¶
noLeadSpace 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 string, emits
type.not.valid. - If the value is a string but starts with whitespace, emits
string.has.leading-whitespace. - If the value is a string that doesn't start with whitespace → returns an empty result set.
Examples¶
Valid string without leading whitespace¶
await noLeadSpace("hello", "$");
// → []
String with leading spaces¶
await noLeadSpace(" hello", "$");
// → [
// JaneEvent{
// kind: "error",
// code: "string.has.leading-whitespace",
// path: "$",
// ...
// }
// ]
Non-string value¶
await noLeadSpace(42, "$");
// → [
// JaneEvent{
// kind: "error",
// code: "type.not.valid",
// path: "$",
// ...
// }
// ]