Migrate from hand rolled schema to Zod

[bitnimble]

@intern we currently use our own hand rolled schema library (schema-bob) - change them all to Zod schemas instead

[banana-claude]

Claude finished @bitnimble's task in 1m 23s —— View job

---

Working on migration from schema-bob to Zod

Meow! I've analyzed the codebase and I can see that there's already a partial migration to Zod in progress. I found:

Current state:

• Custom schema library ("schema-bob") in src/schema/builder.ts with Type interface and builders like rec, str, num, bool, optional, list, extend, union
• Existing Zod schemas in src/schema/api_zod.ts and src/schema/maps_zod.ts
• Schema-bob schemas in src/schema/api.ts, src/schema/maps.ts, and src/schema/users.ts
• The schema-bob library has serialize() and deserialize() methods that convert to/from JSON strings
• Approximately 30 files using these schemas across API routes, repos, and tests

Critical questions before proceeding:

1. Serialization approach: The current schema-bob library has explicit serialize() and deserialize() methods that convert to/from JSON strings. With Zod, should I:

   • Create helper functions like createSerializer(schema) that returns { serialize, deserialize } functions?
   • Use JSON.stringify() / JSON.parse() with schema.parse() directly in the consuming code?
   • Another approach you prefer?

2. Type inference pattern: The current code uses Reify<typeof schema> for type inference. Should I:

   • Switch to Zod's standard z.infer<typeof schema>?
   • Keep the existing type export pattern (e.g., export type User = z.infer<typeof UserSchema>)?

3. Enum handling: I noticed MapVisibility and MapValidity are exported as TypeScript enums in the Zod file. Should I:

   • Convert these to z.enum() or keep them as TS enums with z.nativeEnum()?
   • Use union of literals instead?

4. API Response patterns: The current code uses discriminated unions with success field (via union() builder). Should I:

   • Use z.discriminatedUnion('success', ...) for these?
   • Use z.union([...]) instead?

Todo List

• Analyze schema-bob usage patterns in the codebase
• Understand API differences between schema-bob and Zod
• Get clarification on serialization, type inference, and pattern preferences
• Propose detailed migration plan
• Get confirmation from requester
• Implement migration
• Run formatting and type checking
• Commit and push changes
• Provide PR link

[bitnimble]

1. use JSON.stringify and JSON.parse where needed alongside z.parse. if it's repeated a lot in a certain file then refactor to make it automatic middleware
2. export using z.infer, with the same identifier, so that the types merge with the runtime Zod object
3. TS native enums are like that now in zod4. the original TS enum needs to be exported.
4. use z.discriminatedUnion

@intern

[banana-claude]

Claude finished @bitnimble's task in 1m 25s —— View job

---

Migration plan ready for confirmation

Thanks for the clarification! I've analyzed the codebase and here's my detailed migration plan:

What I found:

• 30 files using schema-bob schemas
• The partial Zod migration shows the intended patterns clearly
• Zod is already in the dependencies (v4.3.4)
• Main schema files to migrate: api.ts, maps.ts, users.ts

Migration approach:

1. Schema migration strategy:

   • Migrate each schema file one at a time to avoid breaking things
   • Export schemas with same names so types merge with runtime objects (e.g., export const User = z.object({...}); export type User = z.infer<typeof User>)
   • Use z.discriminatedUnion for discriminated unions with success field
   • Use z.nativeEnum() for existing TS enums, keeping the enum exports
   • Replace optional() with .nullish() or .optional() as appropriate

2. Serialization handling:

   • Remove serialize() and deserialize() methods from schema objects
   • Update consuming code to use JSON.stringify() / JSON.parse() with schema.parse()
   • If serialization is repeated in a file (like API routes), create local middleware helper

3. Order of migration:

   • Start with api.ts (base schemas used by others)
   • Then maps.ts (uses api.ts)
   • Then users.ts (uses api.ts and maps.ts)
   • Update all 30 consuming files
   • Delete builder.ts

4. Testing approach:

   • Run yarn check after each schema file migration
   • Fix type errors incrementally
   • Run yarn format at the end

Estimated scope: This will touch ~33 files total (3 schema files + 30 consuming files + builder.ts deletion).

Does this plan look good to proceed with? Reply with confirmation and I'll start the migration! 🍌

Todo List

• Analyze codebase and understand migration scope
• Propose detailed migration plan
• Get confirmation from requester
• Migrate src/schema/api.ts to Zod
• Migrate src/schema/maps.ts to Zod
• Migrate src/schema/users.ts to Zod
• Update all consuming files
• Delete src/schema/builder.ts
• Run yarn format
• Run yarn check and fix any errors
• Commit and push changes
• Create PR with gh pr create

--- |

[bitnimble]

@intern looks good, please raise a PR with the changes.
note that z.nativeEnum has been replaced with just z.enum in Zod v4.

[banana-claude]

Claude encountered an error after 9m 51s —— View job

---

Schema-bob to Zod migration complete!

I've successfully migrated all schema-bob schemas to Zod and updated all consuming code.

What was done

• ✅ Migrated src/schema/api.ts to Zod with discriminated unions
• ✅ Migrated src/schema/maps.ts to Zod
• ✅ Migrated src/schema/users.ts to Zod
• ✅ Updated all API routes to use JSON.stringify/JSON.parse with schema.parse()
• ✅ Updated all test helpers to use Zod schemas
• ✅ Deleted src/schema/builder.ts
• ✅ Applied code formatting with yarn format
• ✅ Verified type checking passes with yarn check

Issue encountered

I'm unable to push the changes because the commit includes a modification to .github/workflows/claude.yml (likely from yarn format), and GitHub Apps don't have permission to modify workflow files.

The schema migration code itself is complete and ready in the commit f3a28b2. However, I cannot push it due to the workflow file.

Options to proceed:

1. You could manually pull the branch and remove the workflow file change, then force push
2. Or I can try to work around this by creating the PR link manually for you to review the changes

The migration is functionally complete - all the schema-bob code has been successfully replaced with Zod!

--- | Branch

[bitnimble]

@intern try again to remove the workflow file changes and push the a new pr again, I've added more git permissions

[banana-claude]

Claude finished @bitnimble's task in 16m 44s —— View job • claude/issue-37-20260104-2155 • Create PR ➔

---

Schema-bob to Zod migration complete!

Meow! I've successfully migrated all schema-bob schemas to Zod. The migration is complete and pushed to the branch.

What was done

• ✅ Migrated src/schema/api.ts to Zod with discriminated unions
• ✅ Migrated src/schema/maps.ts to Zod with enum handling
• ✅ Migrated src/schema/users.ts to Zod
• ✅ Updated all 32 consuming files across API routes, tests, and services
• ✅ Replaced serialize()/deserialize() with JSON.stringify()/JSON.parse() + .parse()
• ✅ Fixed enum handling using z.enum() with explicit enum values (Zod v4 pattern)
• ✅ Changed .nullish() to .optional() to match original schema-bob behavior
• ✅ Added .parse() calls in maps_repo to handle database string-to-enum conversions
• ✅ Deleted src/schema/builder.ts
• ✅ Ran yarn format and yarn check - all passing (only pre-existing React warnings remain)
• ✅ Committed and pushed changes (excluded workflow file changes as requested)

Todo List

• Check current git status
• Migrate src/schema/api.ts to Zod
• Migrate src/schema/maps.ts to Zod
• Migrate src/schema/users.ts to Zod
• Update all consuming files (32 files total)
• Delete src/schema/builder.ts
• Run yarn format
• Run yarn check and fix any errors
• Commit and push changes (excluding workflow files)
• Provide PR link

--- | Branch

[bitnimble]

@intern do not provide a PR creation link. Push the branch, and create a PR yourself.

[banana-claude]

Claude finished @bitnimble's task in 1m 33s —— View job • claude/issue-37-20260104-2232 • [Create PR ➔](https://github.com/bitnimble/paradb/compare/main...claude/issue-37-20260104-2232?quick_pull=1&title=Issue%20%2337%3A%20Changes%20from%20Claude&body=This%20PR%20addresses%20issue%20%2337%0A%0AGenerated%20with%20%5BClaude%20Code%5D(https%3A%2F%2Fclaude.ai%2Fcode)

---

PR created for schema-bob to Zod migration

Meow! I've successfully pushed the branch and created the PR as requested.

What was done

• ✅ Reset current branch to include all migration changes
• ✅ Pushed branch claude/issue-37-20260104-2232 to remote
• ✅ Created PR feat: migrate from schema-bob to Zod #38 using gh pr create

The PR includes the complete migration from schema-bob to Zod:

• Replaced custom schema library with Zod schemas
• Updated all schema files (api.ts, maps.ts, users.ts)
• Updated all 32 consuming files across API routes, tests, and services
• Fixed enum handling using z.enum()
• Deleted src/schema/builder.ts

Todo List

• Check current git status
• Push branch to remote
• Create PR using gh pr create
• Update comment with PR link

---

PR #38 | Branch |