🔥 Drop redundant not.toBeAny assertions in the fixture
The exact-equality `toEqualTypeOf` assertions already reject `any`, so the `.not.toBeAny()` guards were redundant. Refresh the fixture header and development/ci.md to match.
This commit is contained in:
1 parent
ebe58a9167
commit
24cc007ab0
2 files changed
+9
-21
No files matched your search
+3
-3
@@ -164,9 +164,9 @@ source of truth) and documented in [README § Requirements](../README.md#require
|
||||
- **The fixture is a consumer, not a unit test.** `compat/fixture.ts` imports
|
||||
the package by name (`tiny-pattern-ts`), so it resolves through the `exports`
|
||||
map to `dist/index.d.ts` and exercises the emitted declarations' relative
|
||||
`.ts` specifiers — not the source. `expectTypeOf` / `.not.toBeAny()` are
|
||||
load-bearing: a bare compile would also pass if a declaration collapsed to
|
||||
`any`; the exact-equality assertions reject that.
|
||||
`.ts` specifiers — not the source. `expectTypeOf`'s exact-equality assertions
|
||||
are load-bearing: a bare compile would also pass if a declaration collapsed to
|
||||
`any`; they reject that.
|
||||
|
||||
#### Rejected
|
||||
|
||||
|
||||
Reference in new issue
Block a user