fix(mutator): match deep set/setIfMissing behavior

[rexxars]

Description

There seems to be a few mismatches between @sanity/mutator and Content Lake:

• In Content Lake, a set/setIfMissing-patch targeting a deep key with missing parents will recursively create an object structure for it
• In @sanity/mutator, it will stop once it encounters a key that is not present in the document.

This PR attempts to align the behavior with what Content Lake does. Please review carefully - my knowledge of the mutator is limited and there may be (edge) cases I have not considered.

Fixes SDX-772.

Edit: I see that arrays also gets overwritten in a similar vein as primitives, but I am not quite sure yet how to resolve it.

What to review

• Mutations work as expected

Notes for release

• Fixed an issue where certain remote patches would not cleanly apply in the studio, requiring a reload of the document in order to see the change

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
performance-studio	✅ Ready (Inspect)	Visit Preview	Oct 23, 2023 9:54pm
test-studio	✅ Ready (Inspect)	Visit Preview	Oct 23, 2023 9:54pm

1 Ignored Deployment

Name	Status	Preview	Updated (UTC)
studio-workshop	⬜️ Ignored (Inspect)		Oct 23, 2023 9:54pm

[github-actions]

No changes to documentation

[github-actions]

Component Testing Report Updated Oct 23, 2023 10:00 PM (UTC)

File	Status	Duration	Passed	Skipped	Failed
formBuilder/ArrayInput.spec.tsx	✅ Passed (Inspect)	8s	3	0	0
formBuilder/inputs/PortableText/Annotations.spec.tsx	✅ Passed (Inspect)	9s	3	0	0
formBuilder/inputs/PortableText/Decorators.spec.tsx	✅ Passed (Inspect)	10s	6	0	0
formBuilder/inputs/PortableText/FocusTracking.spec.tsx	✅ Passed (Inspect)	28s	15	0	0
formBuilder/inputs/PortableText/Input.spec.tsx	✅ Passed (Inspect)	13s	9	0	0
formBuilder/inputs/PortableText/ObjectBlock.spec.tsx	✅ Passed (Inspect)	46s	18	0	0
formBuilder/inputs/PortableText/Styles.spec.tsx	✅ Passed (Inspect)	10s	6	0	0
formBuilder/inputs/PortableText/Toolbar.spec.tsx	✅ Passed (Inspect)	6s	3	0	0

[bjoerge]

Wasn't aware of this behavior with nested set patches. Feels like it should trigger an error, but for now I agree it's more important to align with content lake behavior. Thanks!

[rexxars]

Wasn't aware of this behavior with nested set patches. Feels like it should trigger an error, but for now I agree it's more important to align with content lake behavior. Thanks!

I agree, but I'd say it is unlikely to change in Content Lake given this behavior has always been this way, and maintaining backwards compatible patches is the priority for now.