avoid-anecdotal-types
Avoid Types Based on Anecdotal Data
Overview
Don't infer types from a single example.
If you create a type based on one API response or one sample, you'll miss edge cases. Get authoritative type definitions or examine multiple examples to understand the full shape of your data.
When to Use This Skill
- Creating types for external APIs
- Typing data from databases
- Working with third-party services
- Debugging "impossible" type errors
The Iron Rule
Types should be based on specifications, not samples.
More from marius-townhouse/effective-typescript-skills
precise-any-variants
Use when forced to use any. Use when any is too broad. Use when function types need any.
86narrow-any-scope
Use when any is unavoidable. Use when working with untyped libraries. Use when silencing specific type errors.
35tsdoc-comments
Use when documenting public APIs. Use when writing library code. Use when using JSDoc-style comments. Use when generating documentation. Use when explaining complex types.
34exhaustiveness-checking
Use when handling tagged unions. Use when adding new cases to discriminated unions. Use when switch statements must cover all cases.
13code-gen-independent
Use when confused about types at runtime. Use when trying to use instanceof with interfaces. Use when type errors don't prevent JavaScript output.
12tsconfig-options
Use when setting up a TypeScript project. Use when confused by type checking behavior. Use when strict mode causes unexpected errors.
11