fix(to-json-schema): do not mark exactOptional entry as required JSON property

[sruenwg]

This PR fixes convertSchema to no longer mark exactOptional object properties as required properties in the output JSON Schema.
See playground example — {} is clearly a valid value according to the schema, but the generated JSON Schema would reject this as it requires the k2 property.

[vercel]

@sruenwg is attempting to deploy a commit to the Valibot Team on Vercel.

A member of the Team first needs to authorize it.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/valibot@1220

commit: 2595f60

[fabian-hiller]

Thank you for your contribution! Not sure how we could miss that. I will merge it before releasing the next version of the package.

[sruenwg]

Thanks! 👍

[Copilot]

Pull request overview

This PR fixes a bug where exactOptional object properties were incorrectly marked as required in the generated JSON Schema output. The fix ensures that exactOptional is treated the same way as optional and nullish properties, allowing objects to be valid even when these properties are absent.

Key Changes:

• Added exact_optional check to the condition that determines required properties in object schemas
• Updated test cases to include exactOptional properties and verify they are not marked as required

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
packages/to-json-schema/src/converters/convertSchema/convertSchema.ts	Added exact_optional type check to exclude exactOptional properties from the required array
packages/to-json-schema/src/converters/convertSchema/convertSchema.test.ts	Enhanced tests for object, objectWithRest, looseObject, and strictObject schemas to include exactOptional properties and verify correct handling

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.