Effect-TS/effect effect@4.0.0-beta.105

on GitHub

Patch Changes

• #7087 0418564 Thanks @tim-smart! - Recognize tagged Config and RPC errors across duplicated effect package copies.

• #6827 d334a85 Thanks @jaipaljadeja! - Add bounded 429 retries and custom response header names to HttpClient.withRateLimiter.

• #7084 f0be855 Thanks @tim-smart! - Stop capturing definition-location stack frames in Context.Service.

• #7090 b206fa5 Thanks @tim-smart! - Expose stdinIsTerminal and stdoutIsTerminal effects through the Stdio service.

• #7093 b938c8a Thanks @gcanti! - Add the opt-in reportInput parse option for retaining rejected inputs in enumerable fields on value-bearing schema issues and including them in default formatted messages. Value-bearing issue constructors accept the rejected input and parse options directly, and Schema.Annotations.Issue now supports expected for default messages.

  Schema issues no longer format implicitly through Issue#toString. Use SchemaIssue.makeFormatterDefault() when a human-readable message is needed. The throwing and Promise-based adapters in SchemaParser now use the generic message "Schema validation failed" and expose the structured SchemaIssue.Issue as the error cause; consumers that previously read the formatted error message should inspect and explicitly format that cause instead.

  Schema.makeEffect now returns SchemaIssue.Issue failures instead of wrapping them in SchemaError, and Schema.withConstructorDefault accepts an Effect that fails with SchemaIssue.Issue. Fallible Optic operations return structured SchemaIssue.Issue failures, while schema failures from Schema.toIso and Schema.toDifferJsonPatch use the generic error message and preserve the issue in cause instead of formatting it internally.

• #7097 8525f05 Thanks @tim-smart! - Add Cron.format for converting a Cron instance to a cron expression, with an option to include the seconds field.