@rawan-temo/prisma-zod-generator 3.3.1-config-coercion.0

package/.editorconfig

@@ -0,0 +1,9 @@
+# Editor configuration, see http://editorconfig.org
+root = true
+
+[*]
+charset = utf-8
+indent_style = space
+indent_size = 2
+insert_final_newline = true
+trim_trailing_whitespace = true

package/.env.example

@@ -0,0 +1,22 @@
+# Multi-Provider Test Environment Configuration
+# Copy this file to .env and configure your database connections
+
+# PostgreSQL
+POSTGRESQL_URL="postgresql://user:password@localhost:5432/test"
+
+# MySQL
+MYSQL_URL="mysql://user:password@localhost:3306/test"
+
+# MongoDB
+MONGODB_URL="mongodb://localhost:27017/test"
+
+# SQLite (file-based, no configuration needed)
+SQLITE_URL="file:./test.db"
+
+# SQL Server
+SQLSERVER_URL="sqlserver://localhost:1433;database=test;user=sa;password=password;encrypt=true;trustServerCertificate=true"
+
+# Test Configuration
+TEST_TIMEOUT=30000
+TEST_PARALLEL=false
+TEST_VERBOSE=false

package/.github/CODEOWNERS

@@ -0,0 +1,7 @@
+# Global code owners
+* @omar-dulaimi
+
+# Dependabot PRs
+package.json @omar-dulaimi
+package-lock.json @omar-dulaimi
+.github/workflows/ @omar-dulaimi

package/.github/DISCUSSION_TEMPLATE/general.yml

@@ -0,0 +1,39 @@
+name: Discussion
+about: Start a discussion or ask a question
+labels: ['discussion']
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## 💬 Discussion
+
+        Thanks for starting a discussion! For bugs and feature requests, please use the corresponding issue templates.
+
+        🚨 Sponsor to keep this project active: https://github.com/sponsors/omar-dulaimi
+
+  - type: checkboxes
+    id: preflight
+    attributes:
+      label: Before you post
+      options:
+        - label: I searched existing issues and discussions for duplicates
+          required: true
+        - label: I have starred the repository to support the project ⭐
+          required: true
+
+  - type: input
+    id: topic
+    attributes:
+      label: Topic
+      description: A concise title for your discussion
+    validations:
+      required: true
+
+  - type: textarea
+    id: details
+    attributes:
+      label: Details
+      description: Share your question, ideas, or context
+      placeholder: Include examples, code snippets, or links if helpful
+    validations:
+      required: true

package/.github/FUNDING.yml

@@ -0,0 +1 @@
+github: omar-dulaimi

package/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,90 @@
+name: Bug report
+description: Report a problem to help improve Prisma Zod Generator
+labels: ['kind/bug']
+title: '[Bug]: '
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## 🐛 Bug Report
+
+        Thanks for taking the time to report an issue.
+
+        🚨 Sponsor to keep this project active (faster fixes and responses): [GitHub Sponsors →](https://github.com/sponsors/omar-dulaimi)
+
+  - type: checkboxes
+    id: preflight
+    attributes:
+      label: Before you start
+      options:
+        - label: I searched existing issues and discussions for duplicates
+          required: true
+        - label: I’m using the latest version of prisma-zod-generator
+          required: true
+        - label: I have starred the repository to support the project ⭐
+          required: true
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: A clear and concise description of the bug
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Reproduction
+      description: Steps to reproduce the behavior
+      value: |
+        <!--
+        1. Go to '...'
+        2. Change '...'
+        3. Run '...'
+        4. See error
+        -->
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected behavior
+      description: What did you expect to happen?
+
+  - type: textarea
+    id: prisma
+    attributes:
+      label: Prisma schema / query snippet
+      description: Your Prisma schema or relevant query code (do not include secrets)
+      value: |
+        <!-- Do not include database credentials when sharing your Prisma schema! -->
+    validations:
+      required: true
+
+  - type: textarea
+    id: env
+    attributes:
+      label: Environment
+      description: Where does this problem occur?
+      value: |
+        - OS: <!-- e.g. macOS, Windows, Ubuntu -->
+        - Database: <!-- PostgreSQL, MySQL, MongoDB, SQLite, SQL Server -->
+        - Node.js: <!-- node -v -->
+        - Prisma: <!-- prisma -v (paste in next field too) -->
+    validations:
+      required: true
+
+  - type: textarea
+    id: versions
+    attributes:
+      label: Prisma and related versions
+      description: Output of `npx prisma -v` (and relevant package versions)
+      value: |
+        ```
+        # prisma -v
+
+        ```
+    validations:
+      required: true

package/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Ask a question
+    url: https://github.com/omar-dulaimi/prisma-zod-generator/discussions/new
+    about: Ask questions and discuss with others
+  - name: 💖 Sponsor this project
+    url: https://github.com/sponsors/omar-dulaimi
+    about: Help keep the project actively maintained and support new features

package/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,93 @@
+name: Feature request
+description: Suggest an idea or improvement for Prisma Zod Generator
+labels: ['kind/feature', 'enhancement']
+title: '[Feature]: '
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## 💡 Feature Request
+
+        Thank you for helping improve Prisma Zod Generator.
+
+        🚨 Sponsor to keep this project active: [GitHub Sponsors →](https://github.com/sponsors/omar-dulaimi)
+
+  - type: checkboxes
+    id: preflight
+    attributes:
+      label: Before you start
+      options:
+        - label: I searched existing issues and discussions to avoid duplicates
+          required: true
+        - label: I’m using the latest version of prisma-zod-generator
+          required: true
+        - label: I’m willing to sponsor this work to help keep the project active
+        - label: I can help with a PR (implementation or review)
+        - label: I have starred the repository to support the project ⭐
+          required: true
+
+  - type: input
+    id: summary
+    attributes:
+      label: Summary
+      description: One-line summary of the feature or improvement
+      placeholder: e.g. Add schema variants for public API responses
+    validations:
+      required: true
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem to solve
+      description: What problem does this feature solve? Who is affected?
+      placeholder: Describe the use case and pain points
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: Proposed solution
+      description: Describe the ideal solution. Include example config, Prisma schema, or code if helpful.
+      placeholder: |
+        // Example API / config sketch
+        {
+          "variants": { "public": { "enabled": true } }
+        }
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: What workarounds or alternatives did you try?
+
+  - type: textarea
+    id: impact
+    attributes:
+      label: Impact / use cases
+      description: Who benefits and how? Any metrics or scale considerations?
+
+  - type: input
+    id: links
+    attributes:
+      label: Related issues / links
+      description: Reference issues, PRs, or external resources
+      placeholder: e.g. #123, prior art, docs, blog posts
+
+  - type: dropdown
+    id: breaking
+    attributes:
+      label: Breaking change
+      options:
+        - No
+        - Yes (requires a major release)
+    validations:
+      required: true
+
+  - type: textarea
+    id: extra
+    attributes:
+      label: Additional context
+      description: Add any other context, sketches, or screenshots

package/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,36 @@
+Please see the [contributing guidelines](https://github.com/omar-dulaimi/prisma-zod-generator/blob/master/CONTRIBUTING.md) for how to create and submit a high-quality PR for this repo.
+
+> 💖 Sponsor to keep this project active and maintain faster reviews: https://github.com/sponsors/omar-dulaimi
+
+---
+
+### Description
+
+> Describe the purpose of this PR along with any background information and the impacts of the proposed change. For the benefit of the community, please do not assume prior context.
+>
+> Provide details that support your chosen implementation, including: breaking changes, alternatives considered, changes to the API, etc.
+>
+> If the UI is being changed, please provide screenshots.
+
+
+### References
+
+> Include any links supporting this change such as a:
+>
+> - GitHub Issue/PR number addressed or fixed
+> - StackOverflow post
+> - Related pull requests/issues from other repos
+>
+> If there are no references, simply delete this section.
+
+### Checklist
+
+- [ ] I ran tests locally and they pass
+- [ ] I updated docs or comments where relevant
+- [ ] I added or updated tests for new behavior
+- [ ] I’ve considered performance and backward compatibility
+- [ ] I’ve searched for related issues/PRs
+
+### Sponsor Note (optional)
+
+If your organization relies on this project, please consider sponsoring to support ongoing maintenance and new features: https://github.com/sponsors/omar-dulaimi

package/.github/workflows/README.md

@@ -0,0 +1,97 @@
+# CI/CD Workflows
+
+Three workflows live in this directory. That is the complete list — if something
+is not described here, it does not run.
+
+## `ci.yml` — CI
+
+**Trigger**: push or PR to `master`, gated by a `filter` job that skips the run
+when the range touches only docs, recipes or workflow config *and* no commit
+message carries a release-worthy type.
+
+**`test`** — Node 20.19.0, 22.x, 24.x:
+
+1. `pnpm run gen-example` — build, then generate the example schemas
+2. `pnpm run typecheck`
+3. `pnpm run lint` — reported but `continue-on-error`, so it never blocks
+4. `pnpm test` — every file matched by the vitest `include` glob, not a
+   hand-maintained list, so a new test file cannot be silently left out
+5. `pnpm run test:coverage:ci` — Node 24 only; thresholds calibrated for a
+   checkout *without* the private `src/pro` submodule
+
+No database services are provisioned, and none are needed: the provider suites
+only run `prisma generate`, which never connects.
+
+**`package-test`** — the only job that checks out the private submodule, so the
+only place its checks can run:
+
+1. `pnpm test` — the full suite *with* the submodule present
+2. builds and packages, then `npm pack --dry-run`
+3. `pnpm run test:package-consumer` — installs the tarball into a throwaway
+   project and generates through it
+4. `pnpm run test:typecheck-fixtures` — type-checks emitted Pro UI output
+   against the real MUI, Chakra, Mantine and Pact packages
+
+Step 1 looks redundant against the `test` job and is not. Roughly two dozen
+suites skip themselves when the submodule is absent, which is the case in `test`
+and in every fork, so without this step 20 of the 21 `tests/pro-*.test.ts` files
+executed nowhere in CI at all. It runs the full glob rather than a `pro-*`
+pattern because the pro-prefixed files are not the whole set — `cli-commands`
+and `issue-375-shadcn-form-compat` gate on the submodule too.
+
+This job does not run for forks, so a fork's CI still covers only the
+open-source suites. That is intended: the submodule is private, and the `test`
+job is what a fork can meaningfully run.
+
+## `docs.yml` — Docs
+
+**Trigger**: push to `master` or manual dispatch. Also filtered, so it only
+deploys when the pushed range actually touches the docs site. Builds
+`website/` and deploys it to GitHub Pages.
+
+## `semantic-release.yml` — Release
+
+**Trigger**: push to `master` or manual dispatch; skipped when the head commit
+message contains `[skip ci]`.
+
+Initializes the private submodule, runs `gen-example`, `typecheck`, `lint` and
+`pnpm test`, builds the package, then runs `semantic-release`. Publishing uses
+**npm Trusted Publishing** (OIDC via `id-token: write`), so there is no npm
+token to manage.
+
+## Configuration
+
+**`.releaserc.json`** — conventional commits; changelog generation; publishes
+from `package/`. Release branches: `master`, plus
+`upgrade/prisma-and-dependencies` as a `beta` prerelease line.
+
+## Secrets
+
+Only two, and one is automatic:
+
+- `GITHUB_TOKEN` — provided by GitHub
+- `SUBMODULE_DEPLOY_KEY` — SSH deploy key for the private `src/pro` submodule;
+  required by `package-test` and by the release workflow
+
+## Branch protection
+
+Require the `test` and `package-test` checks on `master`.
+
+## Commit messages
+
+Conventional commits, with a scope: `type(scope): subject`.
+
+`feat` → minor, `fix`/`perf`/`refactor` → patch, `BREAKING CHANGE:` in the
+footer or `!` after the type → major. `docs`, `style`, `test`, `chore`, `ci`
+and `build` do not themselves trigger a release.
+
+## Running the same checks locally
+
+```bash
+pnpm run gen-example
+pnpm run typecheck
+pnpm run lint
+pnpm test
+pnpm test:coverage      # local thresholds, higher than the CI ones
+pnpm run release:dry    # what semantic-release would do
+```

package/.github/workflows/ci.yml

@@ -0,0 +1,270 @@
+name: CI
+
+on:
+  push:
+    branches: [master]
+  pull_request:
+    branches: [master]
+
+jobs:
+  filter:
+    runs-on: ubuntu-latest
+    outputs:
+      should_run: ${{ steps.compute.outputs.should_run }}
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v5
+        with:
+          fetch-depth: 0
+      - name: Decide if CI should run
+        id: compute
+        shell: bash
+        env:
+          EVENT_NAME: ${{ github.event_name }}
+          BASE_REF: ${{ github.base_ref }}
+        run: |
+          set -euo pipefail
+
+          # The release workflow pushes its own commits back to master - the
+          # `chore(release): x.y.z` version bump from @semantic-release/git, and the
+          # workflow-mutations commit after it - both tagged `[skip ci]`. Their contents
+          # are a version bump and a changelog, produced from a tree CI already validated
+          # one commit earlier, and both touch package.json, which is not in the docs-only
+          # pattern below. So every release used to re-run the full three-Node matrix and
+          # package-test on code nothing had changed.
+          #
+          # Honour the marker the release workflow is already writing.
+          HEAD_MSG="$(git log -1 --pretty=%B "${{ github.sha }}" || true)"
+          if [ "$EVENT_NAME" != "pull_request" ] && printf '%s' "$HEAD_MSG" | grep -qF '[skip ci]'; then
+            echo "Head commit is marked [skip ci]; not running."
+            echo "should_run=false" >> "$GITHUB_OUTPUT"
+            exit 0
+          fi
+
+          if [ "$EVENT_NAME" = "pull_request" ] && [ -n "${BASE_REF:-}" ]; then
+            git fetch --no-tags --prune --depth=1 origin "+refs/heads/${BASE_REF}:refs/remotes/origin/${BASE_REF}"
+            RANGE="origin/${BASE_REF}...HEAD"
+          else
+            PREV="${{ github.event.before }}"
+            CUR="${{ github.sha }}"
+            if [ -z "$PREV" ] || [ "$PREV" = "0000000000000000000000000000000000000000" ]; then
+              RANGE="$CUR~1..$CUR"
+            else
+              RANGE="$PREV..$CUR"
+            fi
+          fi
+
+          echo "Using range: $RANGE"
+
+          # Collect changed files in range
+          CHANGED=$(git diff --name-only $RANGE || true)
+          echo "Changed files:\n$CHANGED"
+
+          # Determine if all changes are non-code only
+          # Non-code: docs site, markdown/docs, recipes, images/assets, and workflow config
+          DOCS_ONLY=true
+          if [ -n "$CHANGED" ]; then
+            if echo "$CHANGED" | grep -Ev '^(website/|README\.md$|CHANGELOG\.md$|CLAUDE\.md$|LICENSE$|zodSchemas\.png$|recipes/|\.github/workflows/)' >/dev/null 2>&1; then
+              DOCS_ONLY=false
+            fi
+          fi
+
+          # Check commit messages for allowed types or breaking change
+          HAS_ALLOWED=false
+          if git log --format=%s $RANGE | grep -Ei '^(feat|fix|perf|revert|refactor|test|build|ci)(\(|!:|:)' >/dev/null 2>&1; then
+            HAS_ALLOWED=true
+          elif git log --format=%B $RANGE | grep -q 'BREAKING CHANGE'; then
+            HAS_ALLOWED=true
+          fi
+
+          SHOULD_RUN=false
+          if [ "$DOCS_ONLY" = false ] || [ "$HAS_ALLOWED" = true ]; then
+            SHOULD_RUN=true
+          fi
+
+          echo "docs_only=$DOCS_ONLY"
+          echo "has_allowed=$HAS_ALLOWED"
+          echo "should_run=$SHOULD_RUN"
+          echo "should_run=$SHOULD_RUN" >> "$GITHUB_OUTPUT"
+
+  test:
+    needs: filter
+    if: needs.filter.outputs.should_run == 'true'
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [20.19.0, 22.x, 24.x]
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v5
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v6
+        with:
+          node-version: ${{ matrix.node-version }}
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 10.15.1
+
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile
+
+      - name: Build project
+        run: pnpm run gen-example
+
+      - name: Run type checking
+        run: pnpm run typecheck
+
+      # Reported but not blocking. `|| echo` *and* continue-on-error meant a lint failure
+      # could not even be seen in the job's conclusion; continue-on-error alone still
+      # surfaces it while keeping the build green.
+      - name: Run linting
+        run: pnpm run lint
+        continue-on-error: true
+
+      # `pnpm test` runs every file matched by the vitest include glob, not a
+      # hand-maintained list, so a new test file can never be silently left out of
+      # CI. No database services are required: the provider suites only run
+      # `prisma generate`, they never connect.
+      - name: Run full test suite
+        run: pnpm test
+        timeout-minutes: 45
+
+      # The coverage ratchet, run once rather than on all three Node versions. Thresholds are
+      # calibrated for a checkout without the private Pro submodule — what this job and every
+      # fork has — where 19 files skip. Measured *after* `pnpm run gen-example`, because that build
+      # step writes several hundred generated schemas into src/schemas; counting those (tsconfig
+      # excludes them, the coverage config did not) put CI 10 points below the same measurement
+      # taken locally without them, which is how the first run of this gate failed. They sit below the lower of that and the with-submodule figure
+      # (91.6/88.0/72.5) so the same script passes either way; both were measured before these
+      # numbers were set. Without this step the gate only ever ran when someone remembered to run
+      # it locally.
+      #
+      # Function coverage reads low in both: c8 merges in-process src/*.ts coverage with remapped
+      # lib/*.js coverage, and a method exercised both ways gets two function-map entries, one of
+      # which always reads zero. It is understated by roughly 20 points — treat statements and
+      # branches as the meaningful figures.
+      #
+      # It re-runs the suite under c8 rather than reusing the run above, because c8 has to own
+      # the process tree: most of these tests spawn `prisma generate`, and in-process coverage
+      # cannot see child processes at all.
+      - name: Check coverage thresholds
+        if: matrix.node-version == '24.x'
+        run: pnpm run test:coverage:ci
+        timeout-minutes: 45
+
+  package-test:
+    runs-on: ubuntu-latest
+    needs: test
+    if: github.event_name != 'pull_request' || github.event.pull_request.head.repo.fork == false
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v5
+        with:
+          fetch-depth: 0
+
+      - name: Init Pro submodule
+        env:
+          PRO_KEY: ${{ secrets.SUBMODULE_DEPLOY_KEY }}
+        run: |
+          if [ -z "$PRO_KEY" ]; then
+            echo "SUBMODULE_DEPLOY_KEY secret is not set"
+            exit 1
+          fi
+          if ! command -v ssh-agent >/dev/null; then
+            echo "ssh-agent not available"
+            exit 1
+          fi
+          eval "$(ssh-agent -s)"
+          mkdir -p ~/.ssh
+          ssh_key_path=~/.ssh/id_pro
+          if printf '%s' "$PRO_KEY" | tr -d '\r' | base64 -d > "$ssh_key_path" 2>/dev/null; then
+            echo "Submodule key decoded from base64"
+          else
+            echo "Submodule key not base64-encoded; trying to normalise raw key"
+            printf '%s' "$PRO_KEY" | sed 's/\r//g; s/\\n/\n/g' > "$ssh_key_path"
+          fi
+          chmod 600 "$ssh_key_path"
+          ssh-add "$ssh_key_path"
+          ssh-keyscan github.com >> ~/.ssh/known_hosts
+          git config --global url."git@github.com:".insteadOf "https://github.com/"
+          git submodule sync --recursive
+          git submodule update --init --recursive
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: '24.x'
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 10.15.1
+
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile
+
+      # The whole suite again, and deliberately so: this is the only job that checks out
+      # the private submodule, and roughly two dozen suites skip themselves without it.
+      # The `test` job above has no submodule, so every `tests/pro-*.test.ts` self-skips
+      # there — 20 of the 21 never executed anywhere in CI, and the one that did
+      # (pro-ui-output-compiles) only because it has its own step below. A real failure
+      # in them was invisible until someone ran the suite on a machine with the
+      # submodule checked out.
+      #
+      # It runs the full glob rather than `tests/pro-*.test.ts` because the pro-prefixed
+      # files are not the whole set: cli-commands and issue-375-shadcn-form-compat gate
+      # on the submodule too, and a hand-written pattern would drift the same way the
+      # old curated test script did.
+      #
+      # Placed before packaging so a failure reports quickly, and so it runs against a
+      # normal `lib/` rather than the obfuscated one package.sh produces.
+      - name: Run the full test suite with the Pro submodule
+        run: pnpm test
+        timeout-minutes: 30
+
+      - name: Build and package
+        run: |
+          pnpm run gen-example
+          ./package.sh
+
+      - name: Test package integrity
+        run: |
+          cd package
+          npm pack --dry-run
+
+      # `npm pack --dry-run` above lists what would be shipped without installing any of it, so
+      # nothing here verified that the tarball installs, that its bin entries resolve, or that
+      # `provider = "prisma-zod-generator"` works — the form every doc and every user writes, and
+      # which no test in the suite uses (they all run `node ./lib/generator.js`). This installs the
+      # package into a throwaway project, generates through it, type-checks the output and parses a
+      # payload through an emitted schema.
+      - name: Verify the packaged generator from a consumer project
+        run: pnpm run test:package-consumer
+        timeout-minutes: 15
+
+      # The only job with the private submodule, so the only place these can run. They generate
+      # the Form UX and Contract Testing packs and type-check the result against the real MUI,
+      # Chakra, Mantine and Pact packages, which live in tests/typecheck-fixtures rather than the
+      # root install — 322 transitive packages that nothing else here needs. The test skips
+      # itself when that package is absent, so it was previously never running anywhere.
+      #
+      # Uncompilable emitted output is the most common defect these packs have had, and it is
+      # invisible to every other check.
+      - name: Type-check emitted Pro UI output
+        run: pnpm run test:typecheck-fixtures
+        timeout-minutes: 20
+
+      - name: Upload package artifact
+        uses: actions/upload-artifact@v5
+        with:
+          name: package-build
+          path: package/
+          retention-days: 7