Automatically generate roo-code.d.ts (including type generation via zod-to-ts)

[cte]

Context

I realized that automatically generating the types we need for our external declaration file cleans up a bunch of stuff, including:

• ~750 lines of duplicative TypeScript boilerplate
• A bunch of type-fu assertions to ensure that zod schemas perfectly match existing types (as opposed to inferring the types from the schema)

Given that, I decided to derive and generate the roo-code.d.ts types from our extension code instead of the other way around. This lets us actually infer types from zod schemas (when it's appropriate).

Here's how it works:

• If you need to expose a type in roo-code.d.ts then you simply add a TypeDefinition entry to schemas/index.ts.
• When you commit your changes a script will run to generate clean types in exports/types.ts.
• Types from exports/types.ts can be safely imported by roo-code.ts.
• After the types are generated the .d.ts file is automatically transpiled by tsup (this always should have been automatically generated with tsc or some other build tool).

There are no logic changes in this PR; it's all typing and build tooling.

Implementation

Screenshots

before	after

How to Test

Get in Touch

---

Important

Automates generation of roo-code.d.ts from Zod schemas, streamlining type management and reducing boilerplate.

• Type Generation:
  • Introduces automated generation of roo-code.d.ts using zod-to-ts.
  • Adds generate-types.mts script to generate types from Zod schemas in schemas/index.ts.
  • Updates package.json with generate-types script.
• Schema and Type Management:
  • Moves type definitions to schemas/index.ts and updates imports across multiple files.
  • Removes redundant type definitions from globalState.ts and other files.
  • Updates schemas/__tests__/index.test.ts to test GLOBAL_STATE_KEYS.
• Pre-commit Hook:
  • Adds pre-commit hook in .husky/pre-commit to ensure roo-code.d.ts is up-to-date.
• Miscellaneous:
  • Increases timeout in waitFor function in utils.ts from 30,000 to 60,000.

^{This description was created by for 47f1e60. It will automatically update as commits are pushed.}

[changeset-bot]

🦋 Changeset detected

Latest commit: 47f1e60

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
roo-cline	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[ellipsis-dev]

The pull request is quite large, with 30 files changed, 2173 lines added, and 1231 lines removed. It includes various changes such as adding new scripts for type generation, updating pre-commit hooks, refactoring import paths, and adding new type definitions using zod.

To improve the review process, it might be beneficial to split this pull request into smaller, more focused ones. Here are some suggestions on how to split the changes:

1. Type Generation and Scripts: Separate the changes related to the new type generation script (scripts/generate-types.mts) and the associated updates in package.json and .husky/pre-commit.

2. Refactoring Imports: Group all the changes related to refactoring import paths across different files. This includes updates in files like src/core/config/ContextProxy.ts, src/core/config/ProviderSettingsManager.ts, and others.

3. Schema and Type Definitions: Isolate the changes related to the new type definitions and schema updates using zod, such as those in src/schemas/index.ts and src/exports/types.ts.

By splitting the pull request into these categories, it will be easier to review and ensure that each set of changes is thoroughly examined. Please consider this suggestion if the changes are not tightly interdependent.

[samhvw8]

cool