Fix toggle type annotation refactors for unnamed types

[mattiamanzati]

Summary

• Fixed toggle type annotation refactor to handle unnamed/unresolved types
• Fixed toggle return type annotation refactor to handle unnamed/unresolved types
• Added ts.NodeBuilderFlags.IgnoreErrors flag to allow type node generation even when types contain errors

Problem

Previously, the toggle type annotation refactors would fail when trying to add type annotations to expressions where TypeScript couldn't fully resolve all types in the signature. A common example was:

export const debug = Schema.Struct({
  id: Schema.Option(Schema.Number)
}).make

When attempting to toggle the type annotation, the refactor would fail because the .make accessor has complex unresolved types in its signature.

Solution

By adding the ts.NodeBuilderFlags.IgnoreErrors flag when calling typeToSimplifiedTypeNode, the TypeScript compiler now generates type nodes even when they contain errors or unresolved references. This allows the refactor to work correctly and produce valid type annotations:

export const debug: (props: { readonly id: import("node_modules/effect/dist/dts/Option").Option<number> }, options?: Schema.MakeOptions) => { readonly id: import("node_modules/effect/dist/dts/Option").Option<number> } = Schema.Struct({
  id: Schema.Option(Schema.Number)
}).make

Test Plan

• ✅ Added new test case toggleTypeAnnotation_unnamed.ts that verifies the refactor works with unnamed types
• ✅ All existing tests pass
• ✅ TypeScript compilation succeeds
• ✅ Linting passes

🤖 Generated with Claude Code

[changeset-bot]

🦋 Changeset detected

Latest commit: cbd84ce

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

This PR includes changesets to release 1 package

Name	Type
@effect/language-service	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