Bump the effect group across 1 directory with 6 updates

[dependabot]

Bumps the effect group with 6 updates in the / directory:

Package	From	To
@effect/cli	0.40.1	0.40.2
@effect/experimental	0.21.1	0.21.2
@effect/platform	0.61.1	0.61.2
@effect/platform-browser	0.40.1	0.40.2
@effect/platform-node	0.56.1	0.56.2
@effect/schema	0.70.0	0.70.1

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

• Updated dependencies [3dce357, 657fc48]:
  • @​effect/schema@​0.70.1
  • @​effect/platform@​0.61.2

Changelog

Sourced from @​effect/cli's changelog.

0.40.2

Patch Changes

• Updated dependencies [3dce357, 657fc48]:
  • @​effect/schema@​0.70.1
  • @​effect/platform@​0.61.2

Commits

• 2177fe8 Version Packages (#3389)
• See full diff in compare view

Updates @effect/experimental from 0.21.1 to 0.21.2

Release notes

Sourced from @​effect/experimental's releases.

@​effect/experimental@​0.21.2

Patch Changes

• #3394 5c3a4d0 Thanks @​tim-smart! - ensure DevTools client is shutdown

• Updated dependencies [3dce357, 657fc48]:

  • @​effect/schema@​0.70.1
  • @​effect/platform@​0.61.2
  • @​effect/platform-node@​0.56.2

Changelog

Sourced from @​effect/experimental's changelog.

0.21.2

Patch Changes

• #3394 5c3a4d0 Thanks @​tim-smart! - ensure DevTools client is shutdown

• Updated dependencies [3dce357, 657fc48]:

  • @​effect/schema@​0.70.1
  • @​effect/platform@​0.61.2
  • @​effect/platform-node@​0.56.2

Commits

• 2177fe8 Version Packages (#3389)
• 5c3a4d0 ensure DevTools client is shutdown (#3394)
• See full diff in compare view

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

• Updated dependencies [3dce357, 657fc48]:
  • @​effect/schema@​0.70.1

Changelog

Sourced from @​effect/platform's changelog.

0.61.2

Patch Changes

• Updated dependencies [3dce357, 657fc48]:
  • @​effect/schema@​0.70.1

Commits

• 2177fe8 Version Packages (#3389)
• See full diff in compare view

Updates @effect/platform-browser from 0.40.1 to 0.40.2

Release notes

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

@​effect/platform-browser@​0.40.2

Patch Changes

• Updated dependencies []:
  • @​effect/platform@​0.61.2

Changelog

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

0.40.2

Patch Changes

• Updated dependencies []:
  • @​effect/platform@​0.61.2

Commits

• 2177fe8 Version Packages (#3389)
• See full diff in compare view

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

• 2177fe8 Version Packages (#3389)
• See full diff in compare view

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

• 2177fe8 Version Packages (#3389)
• 3dce357 Enhanced Parsing with TemplateLiteralParser, closes #3307 (#3347)
• 657fc48 Implement DecodingFallbackAnnotation to manage decoding errors (#3346)
• 7411eaa chore: fix DateTime since tags (#3388)
• 8ea4f44 add Concurrency Annotation docs (#3381)
• See full diff in compare view

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