Giulio Canti

This is a bug fix rather than a new issue, previously it was producing invalid values.

I think this is a responsibility that should be handled upstream by fast-check. This isn't the only situation where values might fail to be generated: for example, it can also...

> Is this a comparable example? No, this demonstrates: ```ts import { FastCheck as fc } from "effect" // a filter that is not aligned with the base arbitrary fc.sample(fc.integer({...

@dubzzz thanks for chime in I think fast-check's current behavior is fine, the important thing from our perspective is that we are not using it incorrectly. Ideally (and maybe this...

The `nodenext` option is not required to use io-ts.

I've thought about it based on some principles and my opinion is that the current behavior is correct: ## Principles 1) Transformations do not have any equivalent in JSON Schema,...

Maybe we should first agree on what we call "contextual". > In the above schema, one could annotate the Schema.UUID with a description that says "a user identifier" but per...

@StefanTheWiz this PR https://github.com/Effect-TS/effect/pull/3971 should address your use case. **Your Repro** (using the code from the PR): ```ts import { JSONSchema, Schema } from "effect" const KafkaClientConfig = Schema.Struct({ allowAutoTopicCreation:...

Regarding the names, Vitest (https://vitest.dev/api/) includes the following conditional testing utilities: - `test.skipIf` - `test.runIf` - `describe.skipIf` - `describe.runIf`

How about this? ```ts // Uses the same option name as the CLI // v test.skipIf({ target: ">=5.2" })("isArray", () => { /* omitted */ }); ``` Plus, you can...