Skip to content

fix: normalize null to undefined in ElicitResultSchema content field #1204

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.

Sign up for GitHub

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

Merged
merged 4 commits into from
Dec 1, 2025
Merged

fix: normalize null to undefined in ElicitResultSchema content field #1204

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f7603b3
fix: normalize null to undefined in ElicitResultSchema content field
mattzcarey Dec 1, 2025
d597cbe
linting
mattzcarey Dec 1, 2025
881f2b8
Merge branch 'main' into fix-normalised-elitication-content
mattzcarey Dec 1, 2025
d6adb78
Merge branch 'main' into fix-normalised-elitication-content
mattzcarey Dec 1, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion src/types.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1831,8 +1831,13 @@ export const ElicitResultSchema = ResultSchema.extend({
/**
* The submitted form data, only present when action is "accept".
* Contains values matching the requested schema.
* Per MCP spec, content is "typically omitted" for decline/cancel actions.
* We normalize null to undefined for leniency while maintaining type compatibility.
*/
content: z.record(z.string(), z.union([z.string(), z.number(), z.boolean(), z.array(z.string())])).optional()
content: z.preprocess(
val => (val === null ? undefined : val),
z.record(z.string(), z.union([z.string(), z.number(), z.boolean(), z.array(z.string())])).optional()
)
});

/* Autocomplete */
Expand Down
Loading