LowFile-scopeJavaScript / TypeScript Plug & play

Avoid excessive precision in numeric literals

Detect floating-point numbers with excessive precision. Overly precise numeric literals can cause rounding errors and unexpected behavior in calculations.

Add to Mesrai Open workspace

Why this matters

Floating-point numbers have limited precision. Excessively precise numeric literals can lead to rounding errors and unexpected behavior in calculations.

Bad vs. good

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

Avoid

var c = 999999999999999999999; // Not good, exceeds precision limits
var z = 1.12345678901234567;  // Too precise, may lose accuracy

Prefer

var a = 9;                     // Ok
var b = 999999999999999;       // Ok, within safe limits
var w = 1.12e-4;               // Ok
var y = 1.1234567890123;       // Ok, precise but within limits

More snippets

Bad

var c = 999999999999999999999; // Not good, exceeds precision limits
var z = 1.12345678901234567;  // Too precise, may lose accuracy

Good

var a = 9;                     // Ok
var b = 999999999999999;       // Ok, within safe limits
var w = 1.12e-4;               // Ok
var y = 1.1234567890123;       // Ok, precise but within limits

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

Bad vs. good

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

Avoid

var c = 999999999999999999999; // Not good, exceeds precision limits
var z = 1.12345678901234567;  // Too precise, may lose accuracy

Prefer

var a = 9;                     // Ok
var b = 999999999999999;       // Ok, within safe limits
var w = 1.12e-4;               // Ok
var y = 1.1234567890123;       // Ok, precise but within limits

More snippets

Bad

var c = 999999999999999999999; // Not good, exceeds precision limits
var z = 1.12345678901234567;  // Too precise, may lose accuracy

Good

var a = 9;                     // Ok
var b = 999999999999999;       // Ok, within safe limits
var w = 1.12e-4;               // Ok
var y = 1.1234567890123;       // Ok, precise but within limits

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