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

chore(deps): update dependency effect to v3.10.16 #3074

Merged
merged 1 commit into from
Nov 25, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 25, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
effect (source) 3.10.15 -> 3.10.16 age adoption passing confidence

Release Notes

Effect-TS/effect (effect)

v3.10.16

Patch Changes
  • #​3918 4dca30c Thanks @​gcanti! - Use a specific annotation (AutoTitleAnnotationId) to add automatic titles (added by Struct and Class APIs), instead of TitleAnnotationId, to avoid interfering with user-defined titles.

  • #​3981 1d99867 Thanks @​gcanti! - Stable filters such as minItems, maxItems, and itemsCount should be applied only if the from part fails with a Composite issue, closes #​3980

    Before

    import { Schema } from "effect"
    
    const schema = Schema.Struct({
      a: Schema.Array(Schema.String).pipe(Schema.minItems(1))
    })
    
    Schema.decodeUnknownSync(schema)({}, { errors: "all" })
    // throws: TypeError: Cannot read properties of undefined (reading 'length')

    After

    import { Schema } from "effect"
    
    const schema = Schema.Struct({
      a: Schema.Array(Schema.String).pipe(Schema.minItems(1))
    })
    
    Schema.decodeUnknownSync(schema)({}, { errors: "all" })
    /*
    throws:
    ParseError: { readonly a: an array of at least 1 items }
    └─ ["a"]
       └─ is missing
    */
  • #​3972 6dae414 Thanks @​tim-smart! - add support for 0 capacity to Mailbox

  • #​3959 6b0d737 Thanks @​gcanti! - Remove Omit from the Class interface definition to align type signatures with runtime behavior. This fix addresses the issue of being unable to override base class methods in extended classes without encountering type errors, closes #​3958

    Before

    import { Schema } from "effect"
    
    class Base extends Schema.Class<Base>("Base")({
      a: Schema.String
    }) {
      f() {
        console.log("base")
      }
    }
    
    class Extended extends Base.extend<Extended>("Extended")({}) {
      // Class '{ readonly a: string; } & Omit<Base, "a">' defines instance member property 'f',
      // but extended class 'Extended' defines it as instance member function.ts(2425)
      // @&#8203;ts-expect-error
      override f() {
        console.log("extended")
      }
    }

    After

    import { Schema } from "effect"
    
    class Base extends Schema.Class<Base>("Base")({
      a: Schema.String
    }) {
      f() {
        console.log("base")
      }
    }
    
    class Extended extends Base.extend<Extended>("Extended")({}) {
      // ok
      override f() {
        console.log("extended")
      }
    }
  • #​3971 d8356aa Thanks @​gcanti! - Refactor JSON Schema Generation to Include Transformation Annotations, closes #​3016

    When generating a JSON Schema, treat TypeLiteralTransformations (such as when Schema.optionalWith is used) as a special case. Annotations from the transformation itself will now be applied, unless there are user-defined annotations on the form side. This change ensures that the user's intended annotations are properly included in the schema.

    Before

    Annotations set on the transformation are ignored. However while using Schema.optionalWith internally generates a transformation schema, this is considered a technical detail. The user's intention is to add annotations to the "struct" schema, not to the transformation.

    import { JSONSchema, Schema } from "effect"
    
    const schema = Schema.Struct({
      a: Schema.optionalWith(Schema.String, { default: () => "" })
    }).annotations({
      identifier: "MyID",
      description: "My description",
      title: "My title"
    })
    
    console.log(JSONSchema.make(schema))
    /*
    Output:
    {
      '$schema': 'http://json-schema.org/draft-07/schema#',
      type: 'object',
      required: [],
      properties: { a: { type: 'string' } },
      additionalProperties: false
    }
    */

    After

    Annotations set on the transformation are now considered during JSON Schema generation:

    import { JSONSchema, Schema } from "effect"
    
    const schema = Schema.Struct({
      a: Schema.optionalWith(Schema.String, { default: () => "" })
    }).annotations({
      identifier: "MyID",
      description: "My description",
      title: "My title"
    })
    
    console.log(JSONSchema.make(schema))
    /*
    Output:
    {
      '$schema': 'http://json-schema.org/draft-07/schema#',
      '$ref': '#/$defs/MyID',
      '$defs': {
        MyID: {
          type: 'object',
          required: [],
          properties: [Object],
          additionalProperties: false,
          description: 'My description',
          title: 'My title'
        }
      }
    }
    */

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" in timezone UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link

vercel bot commented Nov 25, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
ark-docs ✅ Ready (Inspect) Visit Preview Nov 25, 2024 1:51am

Copy link

pkg-pr-new bot commented Nov 25, 2024

Open in Stackblitz

bun add https://pkg.pr.new/chakra-ui/ark/@ark-ui/react@3074
bun add https://pkg.pr.new/chakra-ui/ark/@ark-ui/solid@3074
bun add https://pkg.pr.new/chakra-ui/ark/@ark-ui/svelte@3074
bun add https://pkg.pr.new/chakra-ui/ark/@ark-ui/vue@3074

commit: 11eb224

@renovate renovate bot merged commit f30f3d4 into main Nov 25, 2024
9 checks passed
@renovate renovate bot deleted the renovate/effect-3.x branch November 25, 2024 05:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants