Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump the effect group across 1 directory with 3 updates #226

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 17, 2024

Bumps the effect group with 3 updates in the / directory: @effect/platform, @effect/schema and effect.

Updates @effect/platform from 0.49.3 to 0.57.3

Release notes

Sourced from @​effect/platform's releases.

@​effect/platform@​0.57.3

Patch Changes

@​effect/platform-node@​0.51.11

Patch Changes

@​effect/platform@​0.57.2

Patch Changes

@​effect/platform-node@​0.51.10

Patch Changes

@​effect/platform@​0.57.1

Patch Changes

@​effect/platform-node@​0.51.9

Patch Changes

@​effect/platform@​0.57.0

Minor Changes

... (truncated)

Changelog

Sourced from @​effect/platform's changelog.

0.57.3

Patch Changes

0.57.2

Patch Changes

0.57.1

Patch Changes

0.57.0

Minor Changes

Patch Changes

0.56.0

Minor Changes

Patch Changes

... (truncated)

Commits

Updates @effect/schema from 0.66.1 to 0.68.0

Release notes

Sourced from @​effect/schema's releases.

@​effect/schema@​0.68.0

Minor Changes

  • #2906 f6c7977 Thanks @​gcanti! - ## Refactoring of the ParseIssue Model

    The ParseIssue model in the @effect/schema/ParseResult module has undergone a comprehensive redesign and simplification that enhances its expressiveness without compromising functionality. This section explores the motivation and details of this refactoring.

    Enhanced Schema.filter API

    The Schema.filter API has been improved to support more complex filtering that can involve multiple properties of a struct. This is especially useful for validations that compare two fields, such as ensuring that a password field matches a confirm_password field, a common requirement in form validations.

    Previous Limitations:

    Previously, while it was possible to implement a filter that compared two fields, there was no straightforward way to attach validation messages to a specific field. This posed challenges, especially in form validations where precise error reporting is crucial.

    Example of Previous Implementation:

    import { ArrayFormatter, Schema } from "@effect/schema";
    import { Either } from "effect";
    const Password = Schema.Trim.pipe(Schema.minLength(1));
    const MyForm = Schema.Struct({
    password: Password,
    confirm_password: Password,
    }).pipe(
    Schema.filter((input) => {
    if (input.password !== input.confirm_password) {
    return "Passwords do not match";
    }
    }),
    );
    console.log(
    "%o",
    Schema.decodeUnknownEither(MyForm)({
    password: "abc",
    confirm_password: "d",
    }).pipe(Either.mapLeft((error) => ArrayFormatter.formatErrorSync(error))),
    );
    /*
    {
    _id: 'Either',
    _tag: 'Left',
    left: [
    {
    _tag: 'Type',
    path: [],
    message: 'Passwords do not match'

... (truncated)

Changelog

Sourced from @​effect/schema's changelog.

0.68.0

Minor Changes

  • #2906 f6c7977 Thanks @​gcanti! - ## Refactoring of the ParseIssue Model

    The ParseIssue model in the @effect/schema/ParseResult module has undergone a comprehensive redesign and simplification that enhances its expressiveness without compromising functionality. This section explores the motivation and details of this refactoring.

    Enhanced Schema.filter API

    The Schema.filter API has been improved to support more complex filtering that can involve multiple properties of a struct. This is especially useful for validations that compare two fields, such as ensuring that a password field matches a confirm_password field, a common requirement in form validations.

    Previous Limitations:

    Previously, while it was possible to implement a filter that compared two fields, there was no straightforward way to attach validation messages to a specific field. This posed challenges, especially in form validations where precise error reporting is crucial.

    Example of Previous Implementation:

    import { ArrayFormatter, Schema } from "@effect/schema";
    import { Either } from "effect";
    const Password = Schema.Trim.pipe(Schema.minLength(1));
    const MyForm = Schema.Struct({
    password: Password,
    confirm_password: Password,
    }).pipe(
    Schema.filter((input) => {
    if (input.password !== input.confirm_password) {
    return "Passwords do not match";
    }
    }),
    );
    console.log(
    "%o",
    Schema.decodeUnknownEither(MyForm)({
    password: "abc",
    confirm_password: "d",
    }).pipe(Either.mapLeft((error) => ArrayFormatter.formatErrorSync(error))),
    );
    /*
    {
    _id: 'Either',
    _tag: 'Left',
    left: [
    {
    _tag: 'Type',
    path: [],

... (truncated)

Commits
  • ebed962 Version Packages (#3003)
  • f6c7977 Schema: version 0.68.0 (#2906)
  • 368d735 Version Packages (#2996)
  • 0ff11d7 fix typo (isExact -> exact) and make internal toASTAnnotations more gen...
  • 3b15e1b Improve error handling (type-level) for improper usage of optional,… (#2997)
  • 3a750b2 Expose exact option for strict decoding on missing properties, clos… (#2994)
  • 01171bc add internal mergeSchemaAnnotations (#2992)
  • 50fc289 Version Packages (#2973)
  • 2ee4f2b Remove Simplify from extend, pick, omit, pluck APIs, closes… (#2991)
  • e32b5eb Enhance README with guidelines on schema transformations and arbitrar… (#2987)
  • Additional commits viewable in compare view

Updates effect from 3.0.1 to 3.3.4

Release notes

Sourced from effect's releases.

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

  • #2952 eb98c5b Thanks @​KhraksMamtsov! - Change Config.array to return Array<A> instead of ReadonlyArray<A>

  • #2950 184fed8 Thanks @​gcanti! - Ensure Chunk.reverse preserves NonEmpty status, closes #2947

  • #2954 6068e07 Thanks @​jessekelly881! - Fix runtime error in Struct.evolve by enhancing compile-time checks, closes #2953

  • #2948 3a77e20 Thanks @​gcanti! - Remove unnecessary === comparison in getEquivalence functions

    In some getEquivalence functions that use make, there is an unnecessary === comparison. The make function already handles this comparison.

Changelog

Sourced from effect's changelog.

3.3.4

Patch Changes

3.3.3

Patch Changes

3.3.2

Patch Changes

3.3.1

Patch Changes

  • #2952 eb98c5b Thanks @​KhraksMamtsov! - Change Config.array to return Array<A> instead of ReadonlyArray<A>

  • #2950 184fed8 Thanks @​gcanti! - Ensure Chunk.reverse preserves NonEmpty status, closes #2947

  • #2954 6068e07 Thanks @​jessekelly881! - Fix runtime error in Struct.evolve by enhancing compile-time checks, closes #2953

  • #2948 3a77e20 Thanks @​gcanti! - Remove unnecessary === comparison in getEquivalence functions

    In some getEquivalence functions that use make, there is an unnecessary === comparison. The make function already handles this comparison.

3.3.0

Minor Changes

... (truncated)

Commits

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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the effect group with 3 updates in the / directory: [@effect/platform](https://github.com/Effect-TS/effect/tree/HEAD/packages/platform), [@effect/schema](https://github.com/Effect-TS/effect/tree/HEAD/packages/schema) and [effect](https://github.com/Effect-TS/effect/tree/HEAD/packages/effect).


Updates `@effect/platform` from 0.49.3 to 0.57.3
- [Release notes](https://github.com/Effect-TS/effect/releases)
- [Changelog](https://github.com/Effect-TS/effect/blob/main/packages/platform/CHANGELOG.md)
- [Commits](https://github.com/Effect-TS/effect/commits/@effect/[email protected]/packages/platform)

Updates `@effect/schema` from 0.66.1 to 0.68.0
- [Release notes](https://github.com/Effect-TS/effect/releases)
- [Changelog](https://github.com/Effect-TS/effect/blob/main/packages/schema/CHANGELOG.md)
- [Commits](https://github.com/Effect-TS/effect/commits/@effect/[email protected]/packages/schema)

Updates `effect` from 3.0.1 to 3.3.4
- [Release notes](https://github.com/Effect-TS/effect/releases)
- [Changelog](https://github.com/Effect-TS/effect/blob/main/packages/effect/CHANGELOG.md)
- [Commits](https://github.com/Effect-TS/effect/commits/[email protected]/packages/effect)

---
updated-dependencies:
- dependency-name: "@effect/platform"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: effect
- dependency-name: "@effect/schema"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: effect
- dependency-name: effect
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: effect
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jun 17, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Jun 19, 2024

Superseded by #230.

@dependabot dependabot bot closed this Jun 19, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/effect-f867782483 branch June 19, 2024 15:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants