fix(zod): fix array schema traversal in getSchemaForPath #5067
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
🔎 Overview
This PR fixes warnings that occur when describing paths for nested array fields in Zod schemas. The
getSchemaForPathfunction was incorrectly handling array traversal, causing console warnings like:The fixes include:
i <= paths.lengthtoi < paths.lengthelementproperty instead oftypecontinuestatements🤓 Code snippets/examples (if applicable)
With these changes, paths like
buttons[2].linkoritems[0].variants[1].priceare now correctly resolved without warnings.✔ Issues affected
This resolves console warnings when using nested array fields in Zod schemas with vee-validate's
describemethod.