HighFile-scopeJavaScript / TypeScript Plug & play

Avoid the 'any' type

Detect the use of the 'any' type in TypeScript. Using 'any' disables type checking and can lead to runtime errors. Recommend using specific types or generics instead.

Add to Mesrai Open workspace

Why this matters

Using 'any' disables type checking and can lead to runtime errors. Always use specific types or generics to ensure type safety.

Bad vs. good

Side-by-side examples engineers can pattern-match during review.

Avoid

let foo: any = "bar";

Prefer

let foo: string = "bar";

More snippets

Bad

let foo: any = "bar";

Good

let foo: string = "bar";

Related rules

From the same buckets as this rule.

Critical
Avoid equality operators in loop termination conditions
Check if loops use equality operators (== or !=) in termination conditions. These can lead to infinite loops if the condition is never met exactly. Instead, use relational operators like < or > for safer loop termination.
error-handlingreadability-refactor
Critical
Avoid Returning Null in Non-Async Task Methods
Returning null from a Task or Task<T> method causes a NullReferenceException if awaited. Use Task.CompletedTask or Task.FromResult<T>(null) instead.
error-handlingreadability-refactor+1
Critical
Avoid Using Boolean Expressions in `except` Statements
Detect `except` clauses that use `or` or `and` to catch multiple exceptions. This does not work as intended. Recommend using a tuple of exceptions instead.
error-handlingstack-python

Why this matters

Bad vs. good

More snippets

Related rules

Avoid equality operators in loop termination conditions

Avoid Returning Null in Non-Async Task Methods

Avoid Using Boolean Expressions in `except` Statements

Why this matters

Bad vs. good

More snippets

Related rules

Avoid equality operators in loop termination conditions

Avoid Returning Null in Non-Async Task Methods

Avoid Using Boolean Expressions in `except` Statements