LowFile-scopeC# Plug & play

Ensure Consistent Attribute Placement

Check if attributes are consistently placed in the code, maintaining uniform formatting across the project.

Why this matters

Inconsistent placement of attributes can cause confusion and make code harder to read and modify.

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

Avoid

[Obsolete]
public class OldClass {}

[Obsolete("Use NewMethod instead")] public void OldMethod() {}

Prefer

[Obsolete]
public class OldClass {}

[Obsolete("Use NewMethod instead")]
public void OldMethod() {}

Bad

[Obsolete]
public class OldClass {}

[Obsolete("Use NewMethod instead")] public void OldMethod() {}

Good

[Obsolete]
public class OldClass {}

[Obsolete("Use NewMethod instead")]
public void OldMethod() {}

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