cyclomatic-complexity

Reduce cyclomatic complexity by replacing nested validation with guard clauses that return early, removing else after return or throw, and extracting named methods for distinct steps. Keep the happy path unindented at the bottom of the function.

Replace nested ternaries in JSX with early returns from the component for loading, error, and empty states, or extract a named function with an if cascade. This makes the render logic readable and easier to debug and diff.

Complexity of 1-4 is fine, 5-7 warrants looking for early-return wins, 8-10 should be refactored before adding more, and 11+ is hard to test and should be refactored before merging. The metric is a smell, not a hard rule.

Skip refactoring when code is genuinely linear, has one simple if/else, follows framework-imposed structure like single-path route handlers, or is configuration-style data. Never split a clear function just to lower the metric.

Yes, when the boolean branches the entire function body, split it into two separately named functions so callers pick an explicit intent. Keep the flag only when it toggles a small detail like a debug option.