Update zod 3 to zod 4 support in p5.js dev-2.0 #7872
Conversation
- line 325 schema `items` can be access within `def` - line 356 and 360 `_def` is deprecated , use `def` or directly use `options` - line 393 `zodErrorObj.errors[0]` changes to `zodErrorObj.errors[0]` - line 410 `union error` changes to `errors` - line 414 and 459 , `received` changes to `message` ## Important In constants.js, Symbols aren't considered literal values, nor can they be simply compared with ===. This was an oversight in Zod 3.
According to zod 4 , error message are more elaborated
|
🎉 Thanks for opening this pull request! Please check out our contributing guidelines if you haven't already. And be sure to add yourself to the list of contributors on the readme page! |
madhav2348
changed the title
|
Hi @madhav2348 ! Thanks for working on this. From the tests, looks like the zod update in package.json itself isn't part of the PR? |
My apologies, Thank you for figuring out. I was trying to reproduce the failed test case by switching back and forth between Zod 3 and Zod 4 versions to confirm which leads to uncommitted package.json changes. |
to match the test cases - split the error messages, to get a type in line 418 and 462 - `actualType` will never be undefined which is checked in line 394 so make it undefined in line 430 to pass all test cases
I went through the migration docs, but they haven't covered all the changes. The changes I made are by going through the source code of Zod 4. Thank you |
| @@ -230,6 +230,10 @@ function validateParams(p5, fn, lifecycles) { | |||
| param = param?.replace(/^\.\.\.(.+)\[\]$/, '$1'); | |||
|
|
|||
| let schema = generateTypeSchema(param); | |||
| if (!schema || typeof schema.optional !== 'function') { | |||
There was a problem hiding this comment.
Just curious what test case was generating an undefined schema? This works as a fallback, but I wonder if there's potentially a deeper issue needing fixing that this hides.
There was a problem hiding this comment.
In Zod 3, an undefined somehow works fine schema.optional(), but in Zod 4 throws a TypeError , and 181 test cases failed in WebGL, Type and Visual . So using z.any() as safeguard
Internal clip operations do not enable stencil test for future draw cycles
TypeError: Cannot read properties of undefined (reading 'optin')
- /node_modules/.vite/deps/zod_v4.js:2884:86
- /node_modules/.vite/deps/zod_v4.js:2884:56
- /node_modules/.vite/deps/zod_v4.js:464:5
- /node_modules/.vite/deps/zod_v4.js:10325:13
- /node_modules/.vite/deps/zod_v4.js:464:5
- /node_modules/.vite/deps/zod_v4.js:479:5
- /node_modules/.vite/deps/zod_v4.js:10336:10
- /src/core/friendly_errors/param_validator.js:284:26matches expected screenshots
TypeError: schema.optional is not a function
- /src/core/friendly_errors/param_validator.js:238:25
- /src/core/friendly_errors/param_validator.js:276:21
- /src/core/friendly_errors/param_validator.js:276:12
- /src/core/friendly_errors/param_validator.js:274:27
- /src/core/friendly_errors/param_validator.js:271:39
- /src/core/friendly_errors/param_validator.js:538:24
- /src/core/friendly_errors/param_validator.js:569:16This could work by throw an error here to catch real bugs early instead of hiding them with z.any().
Its just a thought, not sure if this would works,
There was a problem hiding this comment.
I tried adding this:
let schema = generateTypeSchema(param);
if (typeof schema.optional !== 'function') {
console.log(param, schema);
}...and then running just that failing test by changing it to test.only(...), and I see this log:
So it looks like z.function() is responsible for this? I think we don't want to turn this into an any type, but rather, figure out how we can keep it a function, but make it possible to be optional. Maybe something is different about how functions are treated in zod 4?
There was a problem hiding this comment.
My bad. In zod 4, the docs say:
'' The result of z.function() is no longer a Zod schema. Instead, it acts as a standalone "function factory" for defining Zod-validated functions. The API has also changed; you define an input and output schema upfront, instead of using args() and .returns() methods. ''
Do you have any suggestions on this? Because any() feels like a brute-force solution.
I was considering a custom wrapper using z.custom(). But would love to hear your thoughts on this
https://zod.dev/v4/changelog?id=zfunction
https://zod.dev/api?id=functions
Resolves #7833
Changes:
itemscan be accessed withindef_defis deprecated, usedefor directly useoptionszodErrorObj.errors[0]changes tozodErrorObj.issues[0]union errorchanges toerrorsreceivedchanges tomessageImportant
constant.js have some variable which are Symbols , according to zod 4, Symbols aren't considered literal values, nor can they be simply compared with ===. This was an oversight in Zod 3.
PR Checklist
npm run lintpasses