migrate-to-shoehorn

To replace unsafe `as` assertions in TypeScript tests with type-safe partials, you can use the `fromPartial()` function from `@total-typescript/shoehorn` to provide only the required object fields while maintaining type compatibility.

The best way to test error paths with invalid data in TypeScript is using `fromAny()` from `@total-typescript/shoehorn`, which preserves autocomplete while allowing you to feed wrong data into negative tests without breaking type checks.

To stop faking 20+ unrelated properties for the TypeScript compiler in unit tests, migrate your test data typing to use `fromPartial()`, which allows you to pass only the subset of fields you care about, like `body.id`, without faking the rest.

Yes, migrating test files to shoehorn requires updating test code to use `fromPartial()` and `fromAny()` with the appropriate import, and then re-running type checks to confirm that your TypeScript compilation succeeds.

You should not use shoehorn outside of test code, as it is explicitly designed for test-only adoption to replace brittle `as Type` and `as unknown as Type` assertions with safer partial data patterns.

Yes, you can convert `as unknown as Type` patterns to `fromAny()` using `@total-typescript/shoehorn`, which intentionally supports feeding invalid data for error-path tests while keeping autocomplete functional.