O.P.Omit + U.Merge — issue with multiple nested omits from a single object

[mesqueeb]

🐞 Bug Report

Describe the bug

Thanks so much yesterday to fix my edge cases with O.P.Pick!

I have one more edge case left in my library related to O.P.Omit + U.Merge.

Reproduce the bug

Signature:

omit<T extends Record<string, any>, K extends string>(
  obj: T,
  keys: F.AutoPath<T, K>[]
): U.Merge<O.P.Omit<T, S.Split<K, '.'>>>

Execution:

const doc = {
    nested: { omit: { yes: 0, no: 0 } },
    secondProp: true,
}

const res4 = omit(doc, ['nested.omit.yes', 'secondProp'])

• typeof res4 is:

Expected behavior

I expected:

typeof res4 // to be equal to { nested: { omit: { no: number } } }

Possible Solution

I'm not sure : S maybe replace U.Merge with something else?

Reproduction

You can clone my production branch of mesqueeb/filter-anything
See the line:

https://github.com/mesqueeb/filter-anything/blob/4b43d7279711df448fc50882088d775dddca0897/test/index.ts#L81

[millsp]

This issue is overlapping with #225 so I'll add priority on it. Sorry for the delays!

[mesqueeb]

@millsp no problem man! you're an angel to the TS community. I won't ever pressure you : )

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.