HighFile-scopeJavaScript / TypeScript Plug & play

Include error context in structured logs

Error logs must include the operation name and relevant identifiers as structured fields, not just a message string.

Why this matters

Context accelerates root-cause analysis and event correlation.

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

Avoid

console.error(err);

Prefer

logger.error('payment failed',{op:'charge',userId,orderId,err});

Bad

console.error(e)

Good

logger.error('op failed', { op, id, err })

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