LowFile-scopeJava Plug & play

Add proper error handling for date parsing

Parse dates with DateTimeFormatter in try/catch and validate expected formats/timezones.

Why this matters

Input dates are error-prone; explicit handling prevents runtime crashes.

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

Avoid

LocalDate.parse(s);

Prefer

try {
  var d = LocalDate.parse(s, DateTimeFormatter.ISO_LOCAL_DATE);
} catch (DateTimeParseException e) {
  return badRequest("invalid date");
}

Bad

ZonedDateTime.parse(s)

Good

try { parse } catch(DateTimeParseException e) { /* handle */ }

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