2 replies

Validating Encoded Values in Part of Schema: Seeking Best Practices

I have a use cases where part of my code needs to work with the

Encoded

Encoded

values, and validation should be limited to that "part" of the schema. By default, when I do something like

Schema.NonEmptyString.pipe(Schema.patter(...))

Schema.NonEmptyString.pipe(Schema.patter(...))

, and I want to "decode" a value using the encoded-schema, e.g. via

Schema.encodedSchema(MySchema)

Schema.encodedSchema(MySchema)

, the NonEmptyString is validated, but not the pattern.

I understand this is expected. I've been wrapping those schemas in a

declare

declare

to force the validation in the Encoded part, see https://effect.website/play/#bd6cb8f1951c for an example.

My question: Is this a hack? Is there a better way to do this?

Effect Community•2mo ago•

2 replies

Validating Encoded Values in Part of Schema: Seeking Best Practices

I have a use cases where part of my code needs to work with the

Encoded

Encoded

values, and validation should be limited to that "part" of the schema. By default, when I do something like

Schema.NonEmptyString.pipe(Schema.patter(...))

Schema.NonEmptyString.pipe(Schema.patter(...))

, and I want to "decode" a value using the encoded-schema, e.g. via

Schema.encodedSchema(MySchema)

Schema.encodedSchema(MySchema)

, the NonEmptyString is validated, but not the pattern.

I understand this is expected. I've been wrapping those schemas in a

declare

declare

to force the validation in the Encoded part, see https://effect.website/play/#bd6cb8f1951c for an example.

My question: Is this a hack? Is there a better way to do this?

Validating Encoded Values in Part of Schema: Seeking Best Practices

Similar Threads

Validating Encoded Values in Part of Schema: Seeking Best Practices

Similar Threads

Similar Threads

Similar Threads