storm-software / acidic

🧪 Acidic is a modeling tool that can be used to describe and generate code for API end points, database tables, type definitions, client components, and so much more!
Apache License 2.0
3 stars 0 forks source link

build(deps): Bump zod-validation-error from 2.1.0 to 3.2.0 #60

Closed dependabot[bot] closed 6 months ago

dependabot[bot] commented 6 months ago

Bumps zod-validation-error from 2.1.0 to 3.2.0.

Release notes

Sourced from zod-validation-error's releases.

v3.2.0

Minor Changes

  • 6b4e8a0: Introduce fromError API which is a less strict version of fromZodError
  • 35a28c6: Add runtime check in fromZodError and throw dev-friendly TypeError suggesting usage of fromError instead

v3.1.0

Minor Changes

  • 3f5e391: Better error messages for zod.function() types

v3.0.3

Patch Changes

  • 2f1ef27: Bundle code as a single index.js (cjs) or index.mjs (esm) file. Restore exports configuration in package.json.

v3.0.2

Patch Changes

  • 24b773c: Revert package.json exports causing dependant projects to fail

v3.0.1

Patch Changes

  • 3382fbc: 1. Fix issue with ErrorOptions not being found in earlier to es2022 typescript configs. 2. Add exports definition to package.json to help bundlers (e.g. rollup) identify the right module to use.

v3.0.0

Major Changes

  • deb4639: BREAKING CHANGE: Refactor ValidationError to accept ErrorOptions as second parameter.

    What changed?

    Previously, ValidationError accepted Array<ZodIssue> as 2nd parameter. Now, it accepts ErrorOptions which contains a cause property. If cause is a ZodError then it will extract the attached issues and expose them over error.details.

    Why?

    This change allows us to use ValidationError like a native JavaScript Error. For example, we can now do:

    import { ValidationError } from 'zod-validation-error';
    

    try { // attempt to do something that might throw an error } catch (err) { throw new ValidationError('Something went deeply wrong', { cause: err }); }

    How can you update your code?

... (truncated)

Changelog

Sourced from zod-validation-error's changelog.

3.2.0

Minor Changes

  • 6b4e8a0: Introduce fromError API which is a less strict version of fromZodError
  • 35a28c6: Add runtime check in fromZodError and throw dev-friendly TypeError suggesting usage of fromError instead

3.1.0

Minor Changes

  • 3f5e391: Better error messages for zod.function() types

3.0.3

Patch Changes

  • 2f1ef27: Bundle code as a single index.js (cjs) or index.mjs (esm) file. Restore exports configuration in package.json.

3.0.2

Patch Changes

  • 24b773c: Revert package.json exports causing dependant projects to fail

3.0.1

Patch Changes

  • 3382fbc: 1. Fix issue with ErrorOptions not being found in earlier to es2022 typescript configs. 2. Add exports definition to package.json to help bundlers (e.g. rollup) identify the right module to use.

3.0.0

Major Changes

  • deb4639: BREAKING CHANGE: Refactor ValidationError to accept ErrorOptions as second parameter.

    What changed?

    Previously, ValidationError accepted Array<ZodIssue> as 2nd parameter. Now, it accepts ErrorOptions which contains a cause property. If cause is a ZodError then it will extract the attached issues and expose them over error.details.

    Why?

    This change allows us to use ValidationError like a native JavaScript Error. For example, we can now do:

    import { ValidationError } from 'zod-validation-error';
    

    try { // attempt to do something that might throw an error

... (truncated)

Commits
  • 499b9ac chore: version packages
  • 35a28c6 chore: add fromZodError runtime check to throw TypeError on bad usage (#296)
  • 6b4e8a0 feat: introduce fromError API (#293)
  • 925dca2 chore: bump zod from 3.23.0 to 3.23.3 (#292)
  • 1605555 chore: bump zod from 3.22.5 to 3.23.0 (#291)
  • b0eb878 chore: bump zod from 3.22.4 to 3.22.5 (#290)
  • f3773ba chore: bump typescript from 5.4.4 to 5.4.5 (#289)
  • ea2b771 chore: bump @​types/node from 20.12.6 to 20.12.7 (#288)
  • b172494 chore: bump @​types/node from 20.12.5 to 20.12.6 (#287)
  • cec6115 chore: bump @​types/node from 20.12.4 to 20.12.5 (#286)
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 6 months ago

Superseded by #64.