search

ccntrq / git-jira-branch

Manage branches for your Jira tickets
https://www.npmjs.com/package/git-jira-branch
MIT License
11 stars 2 forks source link

fix(deps): bump the production-dependencies group with 4 updates #426

Closed dependabot[bot] closed 3 months ago

dependabot[bot] commented 3 months ago

Bumps the production-dependencies group with 4 updates: @effect/cli, @effect/platform, @effect/platform-node and @effect/schema.

Updates @effect/cli from 0.40.1 to 0.40.2

Release notes

Sourced from @​effect/cli's releases.

@​effect/cli@​0.40.2

Patch Changes

Changelog

Sourced from @​effect/cli's changelog.

0.40.2

Patch Changes

Commits


Updates @effect/platform from 0.61.1 to 0.61.2

Release notes

Sourced from @​effect/platform's releases.

@​effect/platform@​0.61.2

Patch Changes

Changelog

Sourced from @​effect/platform's changelog.

0.61.2

Patch Changes

Commits


Updates @effect/platform-node from 0.56.1 to 0.56.2

Release notes

Sourced from @​effect/platform-node's releases.

@​effect/platform-node@​0.56.2

Patch Changes

  • Updated dependencies []:
    • @​effect/platform@​0.61.2
    • @​effect/platform-node-shared@​0.11.2
Changelog

Sourced from @​effect/platform-node's changelog.

0.56.2

Patch Changes

  • Updated dependencies []:
    • @​effect/platform@​0.61.2
    • @​effect/platform-node-shared@​0.11.2
Commits


Updates @effect/schema from 0.70.0 to 0.70.1

Release notes

Sourced from @​effect/schema's releases.

@​effect/schema@​0.70.1

Patch Changes

  • #3347 3dce357 Thanks @​gcanti! - Enhanced Parsing with TemplateLiteralParser, closes #3307

    In this update we've introduced a sophisticated API for more refined string parsing: TemplateLiteralParser. This enhancement stems from recognizing limitations in the Schema.TemplateLiteral and Schema.pattern functionalities, which effectively validate string formats without extracting structured data.

    Overview of Existing Limitations

    The Schema.TemplateLiteral function, while useful as a simple validator, only verifies that an input conforms to a specific string pattern by converting template literal definitions into regular expressions. Similarly, Schema.pattern employs regular expressions directly for the same purpose. Post-validation, both methods require additional manual parsing to convert the validated string into a usable data format.

    Introducing TemplateLiteralParser

    To address these limitations and eliminate the need for manual post-validation parsing, the new TemplateLiteralParser API has been developed. It not only validates the input format but also automatically parses it into a more structured and type-safe output, specifically into a tuple format.

    This new approach enhances developer productivity by reducing boilerplate code and simplifying the process of working with complex string inputs.

    Example (string based schemas)

    import { Schema } from "@effect/schema";

    // const schema: Schema.Schema<readonly [number, "a", string], ${string}a${string}, never>
const schema = Schema.TemplateLiteralParser(
Schema.NumberFromString,
"a",
Schema.NonEmptyString,
);
    

    console.log(Schema.decodeEither(schema)("100ab"));
// { _id: 'Either', _tag: 'Right', right: [ 100, 'a', 'b' ] }
    

    console.log(Schema.encode(schema)([100, "a", "b"]));
// { _id: 'Either', _tag: 'Right', right: '100ab' }

    Example (number based schemas)

    import { Schema } from "@effect/schema";

    // const schema: Schema.Schema<readonly [number, "a"], ${number}a, never>
const schema = Schema.TemplateLiteralParser(Schema.Int, "a");
    

    console.log(Schema.decodeEither(schema)("1a"));
// { _id: 'Either', _tag: 'Right', right: [ 1, 'a' ] }
    

    console.log(Schema.encode(schema)([1, "a"]));
// { _id: 'Either', _tag: 'Right', right: '1a' }

... (truncated)

Changelog

Sourced from @​effect/schema's changelog.

0.70.1

Patch Changes

  • #3347 3dce357 Thanks @​gcanti! - Enhanced Parsing with TemplateLiteralParser, closes #3307

    In this update we've introduced a sophisticated API for more refined string parsing: TemplateLiteralParser. This enhancement stems from recognizing limitations in the Schema.TemplateLiteral and Schema.pattern functionalities, which effectively validate string formats without extracting structured data.

    Overview of Existing Limitations

    The Schema.TemplateLiteral function, while useful as a simple validator, only verifies that an input conforms to a specific string pattern by converting template literal definitions into regular expressions. Similarly, Schema.pattern employs regular expressions directly for the same purpose. Post-validation, both methods require additional manual parsing to convert the validated string into a usable data format.

    Introducing TemplateLiteralParser

    To address these limitations and eliminate the need for manual post-validation parsing, the new TemplateLiteralParser API has been developed. It not only validates the input format but also automatically parses it into a more structured and type-safe output, specifically into a tuple format.

    This new approach enhances developer productivity by reducing boilerplate code and simplifying the process of working with complex string inputs.

    Example (string based schemas)

    import { Schema } from "@effect/schema";

    // const schema: Schema.Schema<readonly [number, "a", string], ${string}a${string}, never>
const schema = Schema.TemplateLiteralParser(
Schema.NumberFromString,
"a",
Schema.NonEmptyString,
);
    

    console.log(Schema.decodeEither(schema)("100ab"));
// { _id: 'Either', _tag: 'Right', right: [ 100, 'a', 'b' ] }
    

    console.log(Schema.encode(schema)([100, "a", "b"]));
// { _id: 'Either', _tag: 'Right', right: '100ab' }

    Example (number based schemas)

    import { Schema } from "@effect/schema";

    // const schema: Schema.Schema<readonly [number, "a"], ${number}a, never>
const schema = Schema.TemplateLiteralParser(Schema.Int, "a");
    

    console.log(Schema.decodeEither(schema)("1a"));
// { _id: 'Either', _tag: 'Right', right: [ 1, 'a' ] }
    

    console.log(Schema.encode(schema)([1, "a"]));
// { _id: 'Either', _tag: 'Right', right: '1a' }

... (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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore 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 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 ` 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 ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions