Bump the effect group with 3 updates

[dependabot]

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

Updates @effect/platform from 0.48.21 to 0.48.27

Release notes

Sourced from @​effect/platform's releases.

@​effect/platform@​0.48.27

Patch Changes

• #2479 c6dd3c6 Thanks @​tim-smart! - Make the file tree provider the fallback in PlatformConfigProvider.layerFileTreeAdd

• #2486 672f137 Thanks @​tim-smart! - accept string as a valid Socket input

• #2486 672f137 Thanks @​tim-smart! - add Socket.runRaw to handle strings directly

• Updated dependencies [42b3651]:

  • @​effect/schema@​0.64.20

@​effect/platform@​0.48.26

Patch Changes

• #2477 365a486 Thanks @​tim-smart! - add PlatformConfigProvider module

  It contains a file tree provider, that can be used to read config values from a file tree.

  For example, if you have a file tree like this:

  config/
    secret
    nested/
      value
  

  You could do the following:

  import { PlatformConfigProvider } from "@effect/platform";
  import { NodeContext } from "@effect/platform-node";
  import { Config, Effect, Layer } from "effect";
  const ConfigProviderLive = PlatformConfigProvider.layerFileTree({
  rootDirectory: /config,
  }).pipe(Layer.provide(NodeContext.layer));
  Effect.gen(function* (_) {
  const secret = yield* _(Config.secret("secret"));
  const value = yield* _(Config.string("value"), Config.nested("nested"));
  }).pipe(Effect.provide(ConfigProviderLive));

@​effect/platform@​0.48.25

Patch Changes

• #2469 d209171 Thanks @​tim-smart! - replace isomorphic-ws with isows

• Updated dependencies [dadc690, 58f66fe, 3cad21d]:

  • [email protected]

... (truncated)

Changelog

Sourced from @​effect/platform's changelog.

0.48.27

Patch Changes

• #2479 c6dd3c6 Thanks @​tim-smart! - Make the file tree provider the fallback in PlatformConfigProvider.layerFileTreeAdd

• #2486 672f137 Thanks @​tim-smart! - accept string as a valid Socket input

• #2486 672f137 Thanks @​tim-smart! - add Socket.runRaw to handle strings directly

• Updated dependencies [42b3651]:

  • @​effect/schema@​0.64.20

0.48.26

Patch Changes

• #2477 365a486 Thanks @​tim-smart! - add PlatformConfigProvider module

  It contains a file tree provider, that can be used to read config values from a file tree.

  For example, if you have a file tree like this:

  config/
    secret
    nested/
      value
  

  You could do the following:

  import { PlatformConfigProvider } from "@effect/platform";
  import { NodeContext } from "@effect/platform-node";
  import { Config, Effect, Layer } from "effect";
  const ConfigProviderLive = PlatformConfigProvider.layerFileTree({
  rootDirectory: /config,
  }).pipe(Layer.provide(NodeContext.layer));
  Effect.gen(function* (_) {
  const secret = yield* _(Config.secret("secret"));
  const value = yield* _(Config.string("value"), Config.nested("nested"));
  }).pipe(Effect.provide(ConfigProviderLive));

0.48.25

Patch Changes

... (truncated)

Commits

• 43c5d93 Version Packages (#2480)
• 75da860 add string to platform ServerRequest.upgradeChannel (#2487)
• 672f137 more support for strings in platform Socket (#2486)
• c6dd3c6 Make the file tree provider the fallback in PlatformConfigProvider.layerFileT...
• 759c5bb Version Packages (#2478)
• 365a486 add PlatformConfigProvider module (#2477)
• 2fc20b3 Version Packages (#2470)
• d209171 replace isomorphic-ws with isows (#2469)
• 7e3e438 Version Packages (#2457)
• 35ad0ba fix exact optional properties type errors (#2463)
• Additional commits viewable in compare view

Updates @effect/schema from 0.64.15 to 0.64.20

Release notes

Sourced from @​effect/schema's releases.

@​effect/schema@​0.64.20

Patch Changes

• #2483 42b3651 Thanks @​gcanti! - Add ParseIssueTitle annotation, closes #2482

  When a decoding or encoding operation fails, it's useful to have additional details in the default error message returned by TreeFormatter to understand exactly which value caused the operation to fail. To achieve this, you can set an annotation that depends on the value undergoing the operation and can return an excerpt of it, making it easier to identify the problematic value. A common scenario is when the entity being validated has an id field. The ParseIssueTitle annotation facilitates this kind of analysis during error handling.

  The type of the annotation is:

  export type ParseIssueTitleAnnotation = (
    issue: ParseIssue,
  ) => string | undefined;

  If you set this annotation on a schema and the provided function returns a string, then that string is used as the title by TreeFormatter, unless a message annotation (which has the highest priority) has also been set. If the function returns undefined, then the default title used by TreeFormatter is determined with the following priorities:

  • identifier
  • title
  • description
  • ast.toString()

  Example

  import type { ParseIssue } from "@effect/schema/ParseResult";
  import * as S from "@effect/schema/Schema";
  const getOrderItemId = ({ actual }: ParseIssue) => {
  if (S.is(S.struct({ id: S.string }))(actual)) {
  return OrderItem with id: ${actual.id};
  }
  };
  const OrderItem = S.struct({
  id: S.string,
  name: S.string,
  price: S.number,
  }).annotations({
  identifier: "OrderItem",
  parseIssueTitle: getOrderItemId,
  });
  const getOrderId = ({ actual }: ParseIssue) => {
  if (S.is(S.struct({ id: S.number }))(actual)) {
  return Order with id: ${actual.id};
  }
  };
  const Order = S.struct({

... (truncated)

Changelog

Sourced from @​effect/schema's changelog.

0.64.20

Patch Changes

• #2483 42b3651 Thanks @​gcanti! - Add ParseIssueTitle annotation, closes #2482

  When a decoding or encoding operation fails, it's useful to have additional details in the default error message returned by TreeFormatter to understand exactly which value caused the operation to fail. To achieve this, you can set an annotation that depends on the value undergoing the operation and can return an excerpt of it, making it easier to identify the problematic value. A common scenario is when the entity being validated has an id field. The ParseIssueTitle annotation facilitates this kind of analysis during error handling.

  The type of the annotation is:

  export type ParseIssueTitleAnnotation = (
    issue: ParseIssue,
  ) => string | undefined;

  If you set this annotation on a schema and the provided function returns a string, then that string is used as the title by TreeFormatter, unless a message annotation (which has the highest priority) has also been set. If the function returns undefined, then the default title used by TreeFormatter is determined with the following priorities:

  • identifier
  • title
  • description
  • ast.toString()

  Example

  import type { ParseIssue } from "@effect/schema/ParseResult";
  import * as S from "@effect/schema/Schema";
  const getOrderItemId = ({ actual }: ParseIssue) => {
  if (S.is(S.struct({ id: S.string }))(actual)) {
  return OrderItem with id: ${actual.id};
  }
  };
  const OrderItem = S.struct({
  id: S.string,
  name: S.string,
  price: S.number,
  }).annotations({
  identifier: "OrderItem",
  parseIssueTitle: getOrderItemId,
  });
  const getOrderId = ({ actual }: ParseIssue) => {
  if (S.is(S.struct({ id: S.number }))(actual)) {
  return Order with id: ${actual.id};
  }
  };

... (truncated)

Commits

• 43c5d93 Version Packages (#2480)
• 42b3651 Schema: add ParseIssueTitle annotation, closes #2482 (#2483)
• a4032fa Schema: clean up: remove useless internal modules (#2481)
• 2fc20b3 Version Packages (#2470)
• 58f66fe Schema: Class API: Added default title annotation to the encoded side (#2471)
• 3cad21d Schema: length now allows expressing a range (#2465)
• 7e3e438 Version Packages (#2457)
• 04e096d Compare with zod (#2430)
• 82e96a6 Version Packages (#2447)
• 8b46fde Schema: add set, setFromSelf, map, mapFromSelf (#2456)
• Additional commits viewable in compare view

Updates effect from 2.4.15 to 2.4.18

Release notes

Sourced from effect's releases.

[email protected]

Patch Changes

• #2473 dadc690 Thanks @​tim-smart! - add Logger.withConsoleLog/withConsoleError apis

  These apis send a Logger's output to console.log/console.error respectively.

  import { Logger } from "effect";
  // send output to stderr
  const stderrLogger = Logger.withConsoleError(Logger.stringLogger);

[email protected]

Patch Changes

• #2461 8fdfda6 Thanks @​tim-smart! - add Inspectable.toStringUnknown/stringifyCircular

• #2462 607b2e7 Thanks @​tim-smart! - remove handled errors from Effect.retryOrElse

• #2461 8fdfda6 Thanks @​tim-smart! - improve formatting of Runtime failures

• #2415 8206caf Thanks @​tim-smart! - add Iterable module

  This module shares many apis compared to "effect/ReadonlyArray", but is fully lazy.

  import { Iterable, pipe } from "effect";
  // Only 5 items will be generated & transformed
  pipe(
  Iterable.range(1, 100),
  Iterable.map((i) => item ${i}),
  Iterable.take(5),
  );

• #2438 7ddd654 Thanks @​mikearnaldi! - Support Heterogeneous Effects in Effect Iterable apis

  Including:

  • Effect.allSuccesses
  • Effect.firstSuccessOf
  • Effect.mergeAll
  • Effect.reduceEffect
  • Effect.raceAll
  • Effect.forkAll

  For example:

... (truncated)

Changelog

Sourced from effect's changelog.

2.4.18

Patch Changes

• #2473 dadc690 Thanks @​tim-smart! - add Logger.withConsoleLog/withConsoleError apis

  These apis send a Logger's output to console.log/console.error respectively.

  import { Logger } from "effect";
  // send output to stderr
  const stderrLogger = Logger.withConsoleError(Logger.stringLogger);

2.4.17

Patch Changes

• #2461 8fdfda6 Thanks @​tim-smart! - add Inspectable.toStringUnknown/stringifyCircular

• #2462 607b2e7 Thanks @​tim-smart! - remove handled errors from Effect.retryOrElse

• #2461 8fdfda6 Thanks @​tim-smart! - improve formatting of Runtime failures

• #2415 8206caf Thanks @​tim-smart! - add Iterable module

  This module shares many apis compared to "effect/ReadonlyArray", but is fully lazy.

  import { Iterable, pipe } from "effect";
  // Only 5 items will be generated & transformed
  pipe(
  Iterable.range(1, 100),
  Iterable.map((i) => item ${i}),
  Iterable.take(5),
  );

• #2438 7ddd654 Thanks @​mikearnaldi! - Support Heterogeneous Effects in Effect Iterable apis

  Including:

  • Effect.allSuccesses
  • Effect.firstSuccessOf
  • Effect.mergeAll
  • Effect.reduceEffect
  • Effect.raceAll
  • Effect.forkAll

... (truncated)

Commits

• 2fc20b3 Version Packages (#2470)
• dadc690 add Logger.withConsoleLog/withConsoleError apis (#2473)
• 7e3e438 Version Packages (#2457)
• 7ddd654 Support Heterogeneous Effects in Effect Iterable apis (#2438)
• 607b2e7 remove handled errors from Effect.retryOrElse (#2462)
• 8fdfda6 improve formatting of Runtime failures (#2461)
• f456ba2 use const type parameter for Config.withDefault (#2460)
• 8206caf add Iterable module (#2415)
• 82e96a6 Version Packages (#2447)
• 5170ce7 Add support for W3C Trace Context propagation (#2445)
• Additional commits viewable 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

[dependabot]

Superseded by #145.