Duplicate Code: Identical Empty Widget Implementations

[github-actions]

Analysis of commit eaf30ea

Summary

Two widget classes (EmptyCard and InitialCard) contain identical implementations with only their class names differing. This duplication creates unnecessary maintenance burden and increases codebase size without providing any functional value.

Duplication Details

Pattern: Identical Empty State Widgets

• Severity: Medium
• Occurrences: 2 instances
• Locations:
  • lib/ui/widgets/empty_card.dart (lines 3-17)
  • lib/ui/widgets/initial_card.dart (lines 3-17)
• Code Sample:

  class EmptyCard extends StatelessWidget {
    const EmptyCard({
      Key? key,
    }) : super(key: key);
  
    `@override`
    Widget build(BuildContext context) {
      return Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: const [],
        ),
      );
    }
  }

Both widgets render the exact same UI: an empty centered column. The only difference is the class name.

Impact Analysis

• Maintainability: Any changes to the empty state pattern must be duplicated across both files, increasing the risk of inconsistent behavior
• Bug Risk: If a bug fix is applied to one widget but not the other, the application will have inconsistent empty states
• Code Bloat: Two files and two classes serve the same purpose, unnecessarily increasing the codebase size

Refactoring Recommendations

1. Consolidate to Single Widget

   • Keep one widget (suggest EmptyCard as it's more semantically clear)
   • Replace all usages of InitialCard with EmptyCard
   • Delete lib/ui/widgets/initial_card.dart
   • Update lib/ui/widgets/widgets.dart barrel file to remove the export
   • Estimated effort: 15-30 minutes
   • Benefits: Eliminates duplication, simplifies maintenance, reduces codebase size

2. Alternative: Make Widget Configurable

   • If different visual treatments are planned in the future, create a single EmptyStateWidget with optional parameters for customization
   • This prevents duplication while maintaining flexibility
   • Estimated effort: 30-45 minutes
   • Benefits: Future-proof design while eliminating current duplication

Implementation Checklist

• Review duplication findings
• Decide between consolidation or configurable approach
• Update lib/ui/pages/home.dart which uses both widgets
• Remove unused widget file
• Update barrel file exports
• Run tests to verify no functionality broken
• Consider adding meaningful content or icons to improve empty state UX

Analysis Metadata

• Analyzed Files: 25 Dart source files
• Detection Method: Manual code comparison of widget implementations
• Commit: eaf30ea
• Analysis Date: 2026-02-20

AI generated by Duplicate Code Detector

To add this workflow in your repository, run gh aw add github/gh-aw/.github/workflows/duplicate-code-detector.md@94662b1dee8ce96c876ba9f33b3ab8be32de82a4. See usage guide.