Allow 'overwriting' fields when using 'merge' on schemas

[justin0mcateer]

The relatively new 'merge' function is very helpful. Thanks for adding that.

We often use the 'merge' function to produce more specific versions of some base type. In this case, it's helpful to be able to narrow certain types in the result of the intersection/merge.

As an example:

type Base = {
type: 'foo' | 'bar',
name: string,
}

type Foo = {
type: 'foo',
name: string,
fooCount: number,
}

type Bar = {
type: 'bar',
name: string,
barSize: 'small' | 'large',
}

Currently, if a field exists in both types provided to 'merge', it throws an error that 'type' is already defined. In Zod, the Schema on the right overrides the Schema on the left. This also allows for creating some type of derived schema where one or two properties are different.

[DZakh]

I'll investigate.

[chenglou]

This would make porting over from Zod easier as it's Zod's behavior: https://zod.dev/?id=merge
Not sure how desirable in the end, and how complex it'd be though

[DZakh]

It shouldn't be difficult if we require them to have the same type.

[chenglou]

Same type wouldn't generalize well right? Like:

const A = S.schema({ kind: 'a' })
const B = S.schema({ kind: 'b' })
const C = S.merge(A, B)

Not sure if that's important

[DZakh]

In this cases these are Literal("a") and Literal("b") which won't merge

[chenglou]

Humm yeah and then you’d need something like Pick and Omit. And rescript kinda struggles with that as seen with #96

[DZakh]

Maybe for v11, I didn't really have a use case for this myself, since in ReScript you design data differently

[DZakh]

I don't know how relevant it is still, but I implemented it in the commit dbe6984

I'll create a release as soon as the PR passes all tests 🫡

[justin0mcateer]

Awesome! We have used the library a bit and are still very interested is making wider use of it.