14 replies

Making objects to match schema when using Value Equality, Data.struct, Schema.Data

As I've been learning Effect, I've been slowing composing solutions using the provided effect components. For example, when created objects that match the encoded side of a schema, I've found it useful to use

<MySchema>.make

<MySchema>.make

to provide type safety when composing objects on the encoded side. This can be especially useful in nested objects.

However, when I use

Schema.transform

Schema.transform

, the resulting schema no longer has .make, or .omit/.pick/.fields, which limits reusability. I'm also finding the same when I use Schema.Data to provide value equality (due to its underlying use of transform).

This now means I don't have the same type safety I had with less complex schema/types.

Schema.Data

Schema.Data

also doesn't appear to be reflected in the returned type, so its possible to pass a nested object without creating it with

Data.struct

Data.struct

and you silently lose value equality as a result. It's not clear if any of this behaviour is 'by design' or an oversight. I'd be interested to understand this better, if anyone can explain.

Playground: https://effect.website/play#1483cc521a46

In the playground example,

foo1

foo1

and

foo2

foo2

are only equal by value if both objects are wrapped in

Data.struct

Data.struct

during initialisation. If I omit the

Data.struct

Data.struct

, there is no type safety warning and the equality will always fail (as the references are different).

I would have hoped that

.make

.make

would still be available and ensure that the

Schema.Data

Schema.Data

transform was applied to ensure that value equality was preserved. Am I just using this wrong?

Effect Documentation

Effect Playground

Making objects to match schema when using Value Equality, Data.struct, Schema.Data

<MySchema>.make

<MySchema>.make

to provide type safety when composing objects on the encoded side. This can be especially useful in nested objects.

However, when I use

Schema.transform

Schema.transform

Schema.Data

Schema.Data

also doesn't appear to be reflected in the returned type, so its possible to pass a nested object without creating it with

Data.struct

Data.struct

foo1

foo1

and

foo2

foo2

are only equal by value if both objects are wrapped in

Data.struct

Data.struct

during initialisation. If I omit the

Data.struct

Data.struct

, there is no type safety warning and the equality will always fail (as the references are different).

I would have hoped that

.make

.make

would still be available and ensure that the

Schema.Data

Schema.Data

transform was applied to ensure that value equality was preserved. Am I just using this wrong?

Effect Documentation

Effect Playground

Making objects to match schema when using Value Equality, Data.struct, Schema.Data

Similar Threads

Making objects to match schema when using Value Equality, Data.struct, Schema.Data

Similar Threads

Similar Threads

Similar Threads