frenck/probatio - CodSpeed

probatio

Blog Docs Changelog

Performance History

Latest Results

Speed up schema construction (#43)

main

5 hours ago

Extract the alias index build to keep the mapping init within the branch limit

frenck/faster-construction

5 hours ago

Speed up schema construction Profiling Home-Assistant-representative schemas showed construction was spending its time on framework plumbing, not validation work. Three changes close the gap (construction went from ~1.5x slower than voluptuous to ~1.3-1.6x faster, with the validation lead unchanged): - Discover whether a schema uses Self during the compile walk instead of a separate full pre-pass. _compile already recurses every mapping, sequence, and key; only a combinator or wrapper (which compiles its own branches) is opaque to it, so Self is detected on that branch node alone. The Self-detection walk was the single largest construction cost; this removes the duplicate traversal with no behavior change. - Classify a mapping key's marker kind once in _make_candidate and reuse the flags, rather than re-running overlapping isinstance checks per attribute. A literal key (the common case) now does one isinstance, not eight. Subtypes are still honored, so a custom marker subclass works. - Build _MappingValidator's derived indexes in a single pass over the candidates instead of six. The alias collision check needs the full literal map, so it stays a small post-step (aliases are rare). Adds compile benchmarks for the nested, leaf-heavy, combinator-heavy, and deeply nested shapes (refactoring the existing NESTED/LEAF_HEAVY schemas into fresh-each-call factories) so CodSpeed gates construction cost, not just validation, going forward.

frenck/faster-construction

5 hours ago

Suggest close enum values on a Coerce miss (#42)

main

5 hours ago

Suggest close enum values on a Coerce miss A Coerce to an enum already lists the valid values on failure; it now also suggests the closest one when the input is a near miss, the same "did you mean ...?" hint In and a mapping schema's unknown key give. The match is against the member values (what Coerce(enum) actually accepts, since it coerces with enum(value)), string values only, so a suggestion always names something that would validate. An IntEnum, a non-string input, or a plain coercion offers nothing. CoerceInvalid gains the candidates attribute, in the same shape as InInvalid and ExtraKeysInvalid, so the three places a value can miss an allowed set carry their close matches the same way. A custom msg still wins the message text while candidates stays populated.

frenck/enum-suggestions

5 hours ago

Add HexInt to parse a hexadecimal integer (#41) ESPHome's hex_int has no Probatio equivalent: the existing Hex validates a hex-encoded string and returns it unchanged (the sibling of Base64), where hex_int parses a hex integer to an int. HexInt fills that gap. It accepts an int (returned unchanged) or a string read base 16 (a leading 0x is optional), so "0x1A", "1a", and 26 all yield 26. A bool is rejected, and anything else raises CoerceInvalid, so the result is always an int. The inverse, formatting an int as a hex string, is output formatting rather than validation, so it stays a one-line Coerce instead of a validator. The field-list codec lists HexInt among the validators with no frontend shape (it serializes to {} rather than raising); the JSON Schema and OpenAPI codecs already render an unrecognized validator as an open schema.

main

7 hours ago

Add HexInt to parse a hexadecimal integer ESPHome's hex_int has no Probatio equivalent: the existing Hex validates a hex-encoded string and returns it unchanged (the sibling of Base64), where hex_int parses a hex integer to an int. HexInt fills that gap. It accepts an int (returned unchanged) or a string read base 16 (a leading 0x is optional), so "0x1A", "1a", and 26 all yield 26. A bool is rejected, and anything else raises CoerceInvalid, so the result is always an int. The inverse, formatting an int as a hex string, is output formatting rather than validation, so it stays a one-line Coerce instead of a validator. The field-list codec lists HexInt among the validators with no frontend shape (it serializes to {} rather than raising); the JSON Schema and OpenAPI codecs already render an unrecognized validator as an open schema.

frenck/hex-int

7 hours ago

Suggest close members and normalize matches in In (#40)

main

8 hours ago

Latest Branches

+17%

Speed up schema construction#43

5 hours ago

ae3f686

frenck/faster-construction

0%

Suggest close enum values on a Coerce miss#42

5 hours ago

fda91a0

frenck/enum-suggestions

0%

Add HexInt to parse a hexadecimal integer#41

7 hours ago

8d6e38f

frenck/hex-int

© 2026 CodSpeed Technology

Home Terms Privacy Docs