Multiple file support

[harlos0517]

Why

This is a proposal for providing multiple file support to ts-to-zod

Related issue: #71

Based on PR #118

The refactoring took place in the generate function, most notable changes:

• the function becomes async because it has been delegated the responsibility of reading the type files
• internally it uses a recursive method ( iterateToZod ) up to the transformation of the zodSchemas
• changes elsewhere are just adjustments to the changes that affect generate

TODO

• non-relative module imports
• verify the following dependency scenarios
  • manage default exports
  • deep nesting, cross reference between modules
  • test scenarios with types, interfaces, enums
  • check to see if we can make generate simpler
  • relay exports, export * from 'asdf'
  • check modules aliasing extensively

This is still WIP so any feedback and ideas are welcome!

[harlos0517]

For now, every test is currently passing.

But there is one case that hasn't been covered by the test.

// color.ts
export enum Secondary { Green, Orange, Violet }
// index.ts
import * as UtilsColor from "./colors/index";
type Enemy = {
  color: UtilsColor.Secondary
}

// index.zod.ts (Desired)
// Generated by ts-to-zod
import { z } from "zod";
import * as UtilsColor from "./colors/index";

export const utilsColorSecondarySchema = z.nativeEnum(UtilsColor.Secondary);

const enemySchema = z.object({
   color: utilsColorSecondarySchema,
});

// index.zod.ts (Current behvaior)
// Generated by ts-to-zod
import { z } from "zod";
import { utilsColorSecondary } from "./colors/index";

export const utilsColorSecondarySchema = z.nativeEnum(Secondary);

const enemySchema = z.object({
   color: utilsColorSecondarySchema,
});

[schiller-manuel]

Can you please rebase? Will review then.

[schiller-manuel]

closing now that we merged #148 and #135