Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(document): allow setting values to undefined with set(obj) syntax with strict: false #15207

Merged
merged 1 commit into from
Jan 30, 2025

Conversation

vkarpov15
Copy link
Collaborator

Fix #15192

Summary

I'm not certain why this !== void 0 check is there, but that behavior doesn't break any of our tests and goes back to at least 2013: be7d978. Likely just a bug that was introduced when adding strict mode that was never fixed.

Examples

@vkarpov15 vkarpov15 added this to the 8.9.6 milestone Jan 27, 2025
@vkarpov15 vkarpov15 merged commit fbd63c7 into master Jan 30, 2025
74 checks passed
@hasezoey hasezoey deleted the vkarpov15/gh-15192 branch January 31, 2025 10:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

doc.set({ field: undefined }) does nothing if the schema has strict: false
2 participants