New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

@badrap/valita

Package Overview
Dependencies
Maintainers
0
Versions
65
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@badrap/valita - npm Package Versions

234567

0.4.3

Diff
badrapbot
published 0.4.3 •

Changelog

Source

0.4.3

Patch Changes

badrapbot
published 0.4.2 •

Changelog

Source

0.4.2

Patch Changes

  • c648586 Thanks @jviide! - Include an array of sub-issues in "invalid_union" issues
badrapbot
published 0.4.1 •

Changelog

Source

0.4.1

Patch Changes

badrapbot
published 0.4.0 •

Changelog

Source

0.4.0

Minor Changes

badrapbot
published 0.3.16 •

Changelog

Source

0.3.16

Patch Changes

  • 59b89be Thanks @arv for reporting this! - Revert changes since v0.3.12 as they were backwards incompatible
badrapbot
published 0.3.15 •

Changelog

Source

0.3.15

Patch Changes

badrapbot
published 0.3.14 •

Changelog

Source

0.3.14

Patch Changes

badrapbot
published 0.3.13 •
badrapbot
published 0.3.12 •

Changelog

Source

0.3.12

Patch Changes

  • 8aaad50 Thanks @jviide! - Mark .optional(() => ...) as non-experimental and recommend it over the now-deprecated .default(x)
badrapbot
published 0.3.11 •

Changelog

Source

0.3.11

Patch Changes

  • f78c082 Thanks @jviide! - Add experimental support for .optional(() => x)

    The .optional() method now supports default value functions for replacing undefined and missing values from the input and wrapped validator. The functionality is similar to .default(x), except that defaultFn has to be a function and is executed for each validation run. This allows patterns like the following:

    const Item = v.object({ id: v.string() });
    
    const Items = v.array(Item).optional(() => []);
    

    This avoids a common pitfall with using .default([]) for the same pattern. As the newly created empty arrays are not shared, mutating them is safe(r) as it doesn't affect other validation outputs.

    This feature is marked experimental for the time being.