LowFile-scopeJava Plug & play

Use @Override for Method Overrides

Ensure that all overridden methods explicitly use the `@Override` annotation.

Why this matters

Omitting `@Override` when overriding methods can lead to accidental method overloading instead of overriding, causing subtle bugs.

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

Avoid

public void equals(Object obj) {
    // Incorrect override
}

Prefer

@Override
public void equals(Object obj) {
    // Correct override
}

Bad

public void equals(Object obj) {
    // Incorrect override
}

Good

@Override
public void equals(Object obj) {
    // Correct override
}

From the same buckets as this rule.

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
Prefer `str.replace()` Over `re.sub()` for Simple Cases
Detect uses of `re.sub()` where regular expressions are not needed. For simple string replacements, `str.replace()` is more efficient and should be used instead.
performance-efficiencystack-python+1
Critical
Use Factory Method Injection in `@Configuration` Classes
Ensure that factory method injection is used in `@Configuration` classes instead of `@Autowired` field injection.
module-architecturestyle-conventions