Skip to content

fix: correct zod import path from 'zod/v4' to 'zod'#25

Merged
amondnet merged 1 commit intomainfrom
fix/zod-import
Dec 22, 2025
Merged

fix: correct zod import path from 'zod/v4' to 'zod'#25
amondnet merged 1 commit intomainfrom
fix/zod-import

Conversation

@amondnet
Copy link
Copy Markdown
Contributor

Summary

Fixes incorrect zod import path in packages/layer/content.config.ts. Changed from non-standard 'zod/v4' import to the correct 'zod' module path.

The schema validator z is now properly imported from the zod package rather than incorrectly from '@nuxt/content'.

Changes

  • Removed z from @nuxt/content import (it was not exported there)
  • Added proper import: import { z } from 'zod'

Test plan

  • Verify TypeScript compilation passes with corrected import
  • Check that zod schema validation still works correctly
  • Run bun typecheck in packages/layer to ensure no type errors

The content.config.ts was importing zod from 'zod/v4' which is not the standard import path. This fixes the import to use the correct 'zod' module path while still properly importing the z validator from a separate statement rather than from @nuxt/content.
@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @amondnet, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses an issue where the z schema validator from the Zod library was being incorrectly imported from @nuxt/content instead of directly from zod. The change ensures that the application correctly resolves the Zod library, preventing potential type errors and ensuring schema validation functions as intended.

Highlights

  • Corrected Zod Import: The import path for the z schema validator has been corrected from an invalid source (@nuxt/content) to the proper zod module.
  • Removed Incorrect Import: The z symbol was removed from the @nuxt/content import statement, as it is not exported by that module.
  • Added Proper Zod Import: A new import statement import { z } from 'zod' was added to correctly bring in the Zod schema validator.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@sonarqubecloud
Copy link
Copy Markdown

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly fixes an import issue with zod in packages/layer/content.config.ts. The change to import z from the zod package instead of @nuxt/content is accurate and necessary for the code to function correctly. I have added one suggestion to improve the organization of the import statements for better readability and maintainability.

@cloudflare-workers-and-pages
Copy link
Copy Markdown

Deploying docs-please with  Cloudflare Pages  Cloudflare Pages

Latest commit: 3352a47
Status:🚫  Deploy failed.

View logs

@amondnet amondnet merged commit 9455e92 into main Dec 22, 2025
1 of 2 checks passed
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.

1 participant